Closed Bug 898888 Opened 11 years ago Closed 11 years ago

Transition manager should use SetStyleContext rather than SetStyleContextWithoutNotification.

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla25

People

(Reporter: dbaron, Assigned: dbaron)

Details

Attachments

(1 file, 1 obsolete file)

      No description provided.
While debugging bug 858937 I noticed that the transition manager was
calling nsIFrame::SetStyleContextWithoutNotification rather than
nsIFrame::SetStyleContext.  SetStyleContextWithoutNotification should
only be used for things that aren't really style changes, but are
instead changes we make during frame construction before things are
really initialized.  Anything that's really a dynamic style change, as
these are, should use SetStyleContext.

I realize I said the opposite in bug 780692 comment 186, and bz said the
same in bug 780692 comment 204, which is why this is the state that it
is.
Attachment #782282 - Flags: review?(ncameron)
Attachment #782281 - Attachment is obsolete: true
Attachment #782281 - Flags: review?(ncameron)
bz, does this make sense to you as well?
Flags: needinfo?(bzbarsky)
Comment on attachment 782282 [details] [diff] [review]
Transition manager should use SetStyleContext rather than SetStyleContextWithoutNotification.

Review of attachment 782282 [details] [diff] [review]:
-----------------------------------------------------------------

Is it worth adding the explanation from your commit message as a comment for SetStyleContextWithoutNotification?
Attachment #782282 - Flags: review?(ncameron) → review+
Hmm.  Yeah, this makes sense.
Flags: needinfo?(bzbarsky)
https://hg.mozilla.org/mozilla-central/rev/cafb82483526
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla25
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: