I see this too in today's nightly. Confirming.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Regression window: Works http://hg.mozilla.org/mozilla-central/rev/699023bb3c9c Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9pre) Gecko/20101222 Firefox/4.0b9pre ID:20101227122945 Fails: http://hg.mozilla.org/mozilla-central/rev/b7acaa08a9c5 Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9pre) Gecko/20101223 Firefox/4.0b9pre ID:20101227124535 Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=699023bb3c9c&tochange=b7acaa08a9c5
blocking2.0: --- → ?
OS: Mac OS X → All
Hardware: x86 → All
Version: unspecified → Trunk
Created attachment 500415 [details] [diff] [review] Fix flag collision. This is caused by a silent merge failure on hg's part when merging the patch in bug 331959 on top of the patch for bug 618196. The result was the same value being used for both flags, so the exception from the onclick handler was treated as preventing anchor actions.
Attachment #500415 - Flags: review?(Olli.Pettay)
Assignee: nobody → bzbarsky
blocking2.0: ? → beta9+
Priority: -- → P1
Whiteboard: [need review]
7 years ago
Attachment #500415 - Flags: review?(Olli.Pettay) → review+
Whiteboard: [need review] → [need landing]
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Whiteboard: [need landing]
Target Milestone: --- → mozilla2.0b9
As per today's meeting, beta 9 will be a time-based release. Marking these all betaN+. Please move it back to beta9+ if you believe it MUST be in the next beta (ie: trunk is in an unshippable state without this)
blocking2.0: beta9+ → betaN+
You need to log in before you can comment on or make changes to this bug.