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)

x86
macOS
defect
Not set
normal

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)

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.
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.
> Do you think it's safe enough? That patch would definitely not be among the scariest I've landed on beta in recent memory.
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?
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....
Attachment #694138 - Flags: review?(justin.lebar+bug)
Assignee: nobody → bzbarsky
Whiteboard: [need review]
Attachment #694139 - Flags: review?(justin.lebar+bug) → review+
Comment on attachment 694138 [details] [diff] [review] Beta backport of fix Ship it.
Attachment #694138 - Flags: review?(justin.lebar+bug) → review+
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?
Whiteboard: [need review] → [need approval]
Flags: in-testsuite+
Whiteboard: [need approval] → [leave open][need approval]
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+
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Whiteboard: [leave open][need approval]
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.
Target Milestone: --- → mozilla20
Verified fixed FF 18 release Win 7 x64.
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: