New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 752024 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Aug 2017
Cc:
shend@chromium.org
█ rjwright@chromium.org
style-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Transition property prevents properties added by an additionnal class to apply at first display

Reported by svn....@gmail.com, Aug 3 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 OPR/46.0.2597.57

Steps to reproduce the problem:
1. Add a transition property to an element (parameters does not matter)
2. Create a class that modify any property handled by the transition
3. Add the created class to the element having the transition peoperty

What is the expected behavior?
Properties added by the additionnal class should apply as expected, with a transition effect.

What went wrong?
Properties added by the additionnal class does not apply at the first display. They apply when properties values are modified by Developer Tools or when the class is removed and added again.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 59.0.3071.109  Channel: n/a
OS Version: Ubuntu 16.04
Flash Version: 

It does not work on Opera either, so Blink might be concerned.
Capture d’écran_2017-08-03_11-10-33.png
283 KB View Download

Comment 1 by svn....@gmail.com, Aug 3 2017 

Additionnal information :
- In this example, the class .isSidebarShown is added by React.
- It works as expected on Safari and Firefox.

Comment 2 by rjwright@chromium.org, Aug 4 2017

Labels: Needs-Feedback
I tried to do the steps that you explained and everything worked as expected. Could you please provide a test case for this problem?
triage_1.html
621 bytes View Download

Comment 3 by svn....@gmail.com, Aug 4 2017 

Unfortunately, I cannot reproduce it simply. I guess this is something related to how React replaces some part of the DOM and how Blink detects these changes, in a very particular case.
The screenshot shows that there is a not interpreted margin (no orange background on the left to show the applied margin) but I cannot provide a test case for that.
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 4 2017

Cc: rjwright@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "rjwright@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by shend@chromium.org, Aug 7 2017

Cc: shend@chromium.org
Status: WontFix (was: Unconfirmed)
Unfortunately, without a test case to reproduce the problem, it's very difficult to track down the issue. I'm marking this as Wont-Fix, but feel free to reopen it if you find a way to help us reproduce the issue.
►

Sign in to add a comment