wildcard (*) applied transition: fill is delayed by depth of nesting
Reported by
tristan....@gmail.com,
Nov 7 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:57.0) Gecko/20100101 Firefox/57.0 Steps to reproduce the problem: 1. set a transition rule for all the elements using the wildcard (*) atribute 2. set a transition-able svg's fill rule 3. trigger the fill-transition What is the expected behavior? The transition should start after transition-delay (0ms by default) What went wrong? The fill transition seems to start after transition-duration * [number of element's ancestors] i.e, if the element has 10 ancestors, and the transition-duration is set to 2s, the transition will start only 20s after expected time. Did this work before? No Does this work in other browsers? Yes Chrome version: Version 62.0.3202.75 (Official Build) (64-bit) Channel: n/a OS Version: OS X 10.12 Flash Version: I didn't tried all transition-able properties, so there might be more.
,
Nov 8 2017
,
Nov 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 8
Still reproducible on ubuntu 70.0.3538.77. Mark it as available. |
||||
►
Sign in to add a comment |
||||
Comment 1 by divya.pa...@techmahindra.com
, Nov 8 2017Labels: Triaged-ET M-64 Needs-Triage-M62 OS-Linux OS-Windows
Status: Untriaged (was: Unconfirmed)