angular2-contextmenu
Advanced tools
Comparing version 0.7.1 to 0.7.2
{ | ||
"typescript.check.workspaceVersion": false | ||
"typescript.check.workspaceVersion": false, | ||
"vsicons.presets.angular": false | ||
} |
@@ -0,1 +1,11 @@ | ||
<a name="0.7.2"></a> | ||
# [0.7.2](https://github.com/isaacplmann/angular2-contextmenu/compare/v0.7.1...v0.7.2) (2017-01-27) | ||
### Bug Fixes | ||
* **closing:** Position contextmenu when parent element has 3d transform | ||
<a name="0.7.1"></a> | ||
@@ -2,0 +12,0 @@ # [0.7.1](https://github.com/isaacplmann/angular2-contextmenu/compare/v0.7.0...v0.7.1) (2017-01-18) |
{ | ||
"name": "angular2-contextmenu", | ||
"version": "0.7.1", | ||
"version": "0.7.2", | ||
"description": "An Angular 2 component to show a context menu on an arbitrary component", | ||
@@ -5,0 +5,0 @@ "main": "angular2-contextmenu.js", |
@@ -234,2 +234,6 @@ # angular2-contextmenu | ||
## CSS Transforms | ||
The context menu will correctly position itself as long as the `<context-menu>` element does not have a parent element that has a complex transform applied to it. Complex in this case means anything besides a simple 2d translation. So rotate, skew, stretch, scale, z-axis translation will all cause the context menu to appear in unexpected places. The common scenario of rendering an element with `transform: translate3d(0px 0px 0px)` in order to trigger the browser's GPU works just fine. | ||
## Deprecated syntax | ||
@@ -236,0 +240,0 @@ |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
100394
1155
287