Closed
Bug 823173
Opened 12 years ago
Closed 12 years ago
nsIDOMNavigatorTime exposed on navigator objects on desktop but xpt is not packaged
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
mozilla20
Tracking | Status | |
---|---|---|
firefox17 | --- | unaffected |
firefox18 | + | verified |
firefox19 | --- | unaffected |
firefox20 | --- | unaffected |
b2g18 | --- | fixed |
People
(Reporter: bzbarsky, Assigned: bzbarsky)
Details
(Keywords: regression)
Attachments
(2 files)
9.07 KB,
patch
|
justin.lebar+bug
:
review+
akeybl
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
1.89 KB,
patch
|
justin.lebar+bug
:
review+
|
Details | Diff | Splinter Review |
This is at least a problem on beta 18. It causes "navigator instanceof Window" to throw instead of returning false.
This was not a problem in 17.
Assignee | ||
Comment 1•12 years ago
|
||
m-c and aurora seem to be unaffected.
Looks like this was fixed on those in bug 807222 part 2.
Justin what should we do for 18 here? Just backport that patch? Do you think it's safe enough?
Triage info: this can cause web compat issues due to scripts throwing exceptions when they shouldn't.
status-firefox17:
--- → unaffected
status-firefox18:
--- → affected
status-firefox19:
--- → unaffected
status-firefox20:
--- → unaffected
Comment 2•12 years ago
|
||
> Do you think it's safe enough?
That patch would definitely not be among the scariest I've landed on beta in recent memory.
Comment 3•12 years ago
|
||
We're in our final beta though, and we haven't heard of any major web compat issues at this point. That's not to say we won't on release, but we need to be very very cautious here. What's the worst thing that can happen if an uplift of bug 807222 part 2 regresses?
Assignee | ||
Comment 4•12 years ago
|
||
I don't think anything bad can happen on non-b2g, for what it's worth. If it compiles to start with, it'll be strictly better than what we have now, as far as I can tell....
Assignee | ||
Comment 5•12 years ago
|
||
Attachment #694138 -
Flags: review?(justin.lebar+bug)
Assignee | ||
Comment 6•12 years ago
|
||
Attachment #694139 -
Flags: review?(justin.lebar+bug)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → bzbarsky
Whiteboard: [need review]
Updated•12 years ago
|
Attachment #694139 -
Flags: review?(justin.lebar+bug) → review+
Comment 7•12 years ago
|
||
Comment on attachment 694138 [details] [diff] [review]
Beta backport of fix
Ship it.
Attachment #694138 -
Flags: review?(justin.lebar+bug) → review+
Assignee | ||
Comment 8•12 years ago
|
||
Comment on attachment 694138 [details] [diff] [review]
Beta backport of fix
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Some b2g landing sometime
User impact if declined: Some websites will break in Firefox 18 that worked in
Firefox 17. How many, unclear.
Testing completed (on m-c, etc.): This patch has been on 19 and 20 for a while
now.
Risk to taking this patch (and alternatives if risky): Risk is low. The other
option is to ship the known-broken behavior.
String or UUID changes made by this patch: None
Attachment #694138 -
Flags: approval-mozilla-beta?
Assignee | ||
Updated•12 years ago
|
Whiteboard: [need review] → [need approval]
Assignee | ||
Comment 9•12 years ago
|
||
Checked in test on inbound and aurora:
https://hg.mozilla.org/integration/mozilla-inbound/rev/85055fcfb211
https://hg.mozilla.org/releases/mozilla-aurora/rev/eaccb5edc854
Flags: in-testsuite+
Whiteboard: [need approval] → [leave open][need approval]
Comment 10•12 years ago
|
||
Updated•12 years ago
|
Comment 11•12 years ago
|
||
Comment on attachment 694138 [details] [diff] [review]
Beta backport of fix
We've weighed your risk/reward analysis and agree that this is a good fix for FF18, especially given the extra flex week in this cycle. Please land no later than 12/26.
Attachment #694138 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Assignee | ||
Comment 12•12 years ago
|
||
Pushed patch and test to beta:
https://hg.mozilla.org/releases/mozilla-beta/rev/5b900eea305f
https://hg.mozilla.org/releases/mozilla-beta/rev/3fa6dcc664fc
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [leave open][need approval]
Assignee | ||
Comment 13•12 years ago
|
||
And https://hg.mozilla.org/releases/mozilla-beta/rev/3094a79aa73b to disable the new test on Android, because on beta their xpt situation is all broken. See bug 807222 part 5.
Comment 14•12 years ago
|
||
Comment 15•12 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/5b900eea305f
https://hg.mozilla.org/releases/mozilla-b2g18/rev/3fa6dcc664fc
https://hg.mozilla.org/releases/mozilla-b2g18/rev/3094a79aa73b
https://hg.mozilla.org/releases/mozilla-b2g18/rev/48da39be33e1
status-b2g18:
--- → fixed
Updated•12 years ago
|
Target Milestone: --- → mozilla20
Comment 16•12 years ago
|
||
Verified fixed FF 18 release Win 7 x64.
Comment 17•12 years ago
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•