Closed
Bug 743666
Opened 13 years ago
Closed 12 years ago
Figure out what to do about XHR.onuploadprogress
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla16
People
(Reporter: Ms2ger, Assigned: peterv)
References
Details
(Keywords: regression)
Attachments
(1 file, 1 obsolete file)
7.43 KB,
patch
|
bzbarsky
:
review+
lsblakk
:
approval-mozilla-aurora+
lsblakk
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
This attribute is well hidden on nsIJSXMLHttpRequest; so well hidden, in fact, that it got lost in the Paris Bindings.
Not sure if we want to keep it, but we should make a call one way or the other.
Comment 1•13 years ago
|
||
Requesting tracking for the moment; we don't want to accidentally ship "something" here without making a considered decision.
tracking-firefox14:
--- → ?
Keywords: regression
I can think of two options:
1. Put the property back and make both onuploadprogress and
addEventListener("uploadprogress", ...) work, but make them warn when used.
phase them out once we feel that we've given enough headsup.
2. Add warnings on aurora and maybe even beta branches *now* so that we have 12
weeks of warnings before we ship with uploadprogress removed.
And if we choose to do 1, i'm ok with onuploadprogress being exposed in workers as long as we make setting it there throw.
Comment 4•13 years ago
|
||
I think #1 is what we should do, per the discussion in today's meeting.
There's been talk of being able to declare things mainthreadonly, so imho we should use that here.
Updated•13 years ago
|
Comment 5•13 years ago
|
||
I'm not sure who's on point for fixing this in FF14 - sending over to jst to help find an assignee.
Assignee: nobody → jst
Comment 6•13 years ago
|
||
Peter, can you look into this one? We need this for current Aurora.
Assignee: jst → peterv
Comment 7•12 years ago
|
||
[Triage Comment]
Merge of 14 to the Beta channel is coming up tomorrow. Is there any risk related to this issue if we are shipping 14 to a wider (beta) audience?
Yeah, we need to fix this, preferably before we ship a beta release.
Assignee | ||
Comment 9•12 years ago
|
||
Need to add a test.
Assignee | ||
Comment 10•12 years ago
|
||
Attachment #629635 -
Attachment is obsolete: true
Attachment #629772 -
Flags: review?(bzbarsky)
Comment 11•12 years ago
|
||
Comment on attachment 629772 [details] [diff] [review]
v1
r=me
We should file a followup for removing this.
Attachment #629772 -
Flags: review?(bzbarsky) → review+
Reporter | ||
Comment 12•12 years ago
|
||
Filed bug 761278
Comment 13•12 years ago
|
||
Comment on attachment 629772 [details] [diff] [review]
v1
[Triage Comment]
Approving for landing on mozilla-beta (now that we have migrated). Will set tracking 15 on the bug filed for making sure this gets turned off again.
Attachment #629772 -
Flags: approval-mozilla-beta+
Comment 14•12 years ago
|
||
status-firefox14:
--- → fixed
Comment 15•12 years ago
|
||
status-firefox15:
--- → affected
tracking-firefox15:
--- → ?
Flags: in-testsuite+
Target Milestone: --- → mozilla16
Comment 16•12 years ago
|
||
Comment on attachment 629772 [details] [diff] [review]
v1
[Approval Request Comment]
Bug caused by (feature/regressing bug #): Bug 740069
User impact if declined: Possible extension (and less likely site) breakage
Testing completed (on m-c, etc.): Passes automated tests.
Risk to taking this patch (and alternatives if risky): Very low risk: just adds a property with a simple implementation to the WebIDL for XMLHttpRequest.
String or UUID changes made by this patch: None.
Attachment #629772 -
Flags: approval-mozilla-aurora?
Comment 17•12 years ago
|
||
Comment on attachment 629772 [details] [diff] [review]
v1
Approving low risk fix, and it's already green (for the most part) on mozilla-beta too.
Attachment #629772 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Comment 18•12 years ago
|
||
(In reply to Boris Zbarsky (:bz) from comment #16)
> String or UUID changes made by this patch: None.
This wasn't quite accurate, afaics - the patch added a string. And sure enough, this has already triggered questions on the l10n list.... it would have been good to give them a heads-up.
Comment 19•12 years ago
|
||
Grmpf, this is soo much easier to message when it can be posted before landing.
I'll allow it, weird edge on the web, string only showing in the error console.
This needs to land on aurora still, too?
Comment 20•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 21•12 years ago
|
||
Yikes. That's what I get for doing this stuff while half asleep. :(
I can just drop all the string stuff from the patch for Aurora and back it out on Beta if preferred. It's not essential to the patch; it would just delay the warning by a cycle (or two if we drop it from Aurora). Axel, what would you prefer here?
Comment 22•12 years ago
|
||
Leave it as is, better to have the ability to localize it than not. Also, flod already localized it on beta, so we're not helping with a revert at this point.
Also, land with the string on aurora.
Comment 23•12 years ago
|
||
OK, that works. Thanks! And sorry for all the trouble. :(
Comment 24•12 years ago
|
||
Updated•12 years ago
|
Comment 25•12 years ago
|
||
Verified as fixed on:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20100101 Firefox/15.0
Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20100101 Firefox/15.0
Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0
XHR.onuploadprogress still works and the user gets a warning in the Error console about it being deprecated.
Updated•12 years ago
|
Component: DOM: Mozilla Extensions → DOM
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
•