Title: ng-animate-ref - Clone doesn't copy contextual styling of original · Issue #12402 · angular/angular.js · GitHub
Open Graph Title: ng-animate-ref - Clone doesn't copy contextual styling of original · Issue #12402 · angular/angular.js
X Title: ng-animate-ref - Clone doesn't copy contextual styling of original · Issue #12402 · angular/angular.js
Description: When an ng-animate-ref element is cloned before an animation, I would expect it to look exactly the same as its source element. Instead, when the source element has styling applied because of the specific context it is in (e.g. .context ...
Open Graph Description: When an ng-animate-ref element is cloned before an animation, I would expect it to look exactly the same as its source element. Instead, when the source element has styling applied because of the s...
X Description: When an ng-animate-ref element is cloned before an animation, I would expect it to look exactly the same as its source element. Instead, when the source element has styling applied because of the s...
Opengraph URL: https://github.com/angular/angular.js/issues/12402
X: @github
Domain: patch-diff.githubusercontent.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"ng-animate-ref - Clone doesn't copy contextual styling of original","articleBody":"When an ng-animate-ref element is cloned before an animation, I would expect it to look exactly the same as its source element. Instead, when the source element has styling applied because of the specific context it is in (e.g. `.context .source-element { background: green; }`), this styling is not applied to the cloned element.\n\nThis makes the animation weird: it first snaps to the styling the .source-element would have when in no context, and then animates to its new context. Example: http://plnkr.co/edit/AXzKmQcE5BUx4NXg4cCS?p=preview. When clicking an element, it first snaps to a blue background, before animating to a black background. I would expect it to animate directly from a green to a black background.\n\nThis can be worked around by simply applying all styling directly to the source element to be animated (e.g. `.source-element-in-context { background: green; }` (see this plunker: http://plnkr.co/edit/Odho9WnoOm9JFv3gzzZl?p=preview), but it makes much more sense to me when angular itself applies all styling of the source element to the cloned element.\n","author":{"url":"https://github.com/dweerd","@type":"Person","name":"dweerd"},"datePublished":"2015-07-22T10:06:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/12402/angular.js/issues/12402"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:d5b746c3-05bf-1053-52c0-6c9508ed2088 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9A70:BE940:599A59F:7925579:696E209D |
| html-safe-nonce | 421f267e9d1416f12af8d1fd35f477d67e442a8a34b5eb01c08dcb68e469d8e8 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5QTcwOkJFOTQwOjU5OUE1OUY6NzkyNTU3OTo2OTZFMjA5RCIsInZpc2l0b3JfaWQiOiIzOTMzNjMzODIwODcwMTg5MjEzIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 32bc1e82ec8b0e6cb9a46912f3d45e92bc6bfa47355640abb5f3f1aefe33b304 |
| hovercard-subject-tag | issue:96527043 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular.js/12402/issue_layout |
| twitter:image | https://opengraph.githubassets.com/7c2eedc8d394fa7c18c18e4df4032e8c9fed1bb4b6737245818c36c8110e375a/angular/angular.js/issues/12402 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/7c2eedc8d394fa7c18c18e4df4032e8c9fed1bb4b6737245818c36c8110e375a/angular/angular.js/issues/12402 |
| og:image:alt | When an ng-animate-ref element is cloned before an animation, I would expect it to look exactly the same as its source element. Instead, when the source element has styling applied because of the s... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | dweerd |
| hostname | github.com |
| expected-hostname | github.com |
| None | 2fbe8cba5e260284c10af515699ff9bb2d6ace05ab6c2e2e585b71d93b2812c3 |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular.js git https://github.com/angular/angular.js.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 460078 |
| octolytics-dimension-repository_nwo | angular/angular.js |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 460078 |
| octolytics-dimension-repository_network_root_nwo | angular/angular.js |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 7fb3bc5c995a876085291706b75cf9b08900c338 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width