Closed Bug 54150 Opened 25 years ago Closed 25 years ago

Style hint for moz-binding should be framechange, not reflow

Categories

(Core :: XBL, defect, P2)

x86
Windows 98
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: hyatt, Assigned: hyatt)

Details

(Keywords: regression, Whiteboard: [rtm-] FIXED ON TRUNK)

A regression was caused recently in the whole property shuffle. The style hint for moz-binding has been changed to reflow when it was originally framechange.
This is a no-brainer one-line fix to undo the regression. Nominating for rtm. I have the fix in hand.
Status: NEW → ASSIGNED
Keywords: regression, rtm
Regression? It's been REFLOW ever since it was added by hyatt%netscape.com in rev 1.7 of nsCSSPropList.h .
That said, FRAMECHANGE does make sense...
Weird. Maybe I just had a mental hiccup and thought I'd done it right to start with. Anyway, it's supposed to be FRAMECHANGE.
We want XBL to work with HTML, and this is a trivial one-line fix. Marking rtm need info; need to attach patch, and get reviewers to put a=/r= in bug to be considered.
Whiteboard: [rtm+ need info]
Whiteboard: [rtm+ need info] → [rtm+ need info] FIXED ON TRUNK
Priority: P3 → P2
This has had a=waterson and r=ben. It's completely low-risk and won't cause any problems.
Whiteboard: [rtm+ need info] FIXED ON TRUNK → [rtm+] FIXED ON TRUNK
PDT marking [rtm-] because not very many folks will encounter problems with XBL in the first version of Netscape 6. PDT is focused on crash/data loss at this point.
Whiteboard: [rtm+] FIXED ON TRUNK → [rtm-] FIXED ON TRUNK
Turns out that the reframe happens anyway, so I guess I don't need to fix this.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.