Kill DOM L&S with fire

RESOLVED FIXED in mozilla5

Status

()

Core
DOM
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: Ms2ger, Assigned: Ms2ger)

Tracking

Trunk
mozilla5
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Assignee)

Description

7 years ago
We've never implemented any of L&S, except for, unfortunately, LSProgressEvent. Keeping the idls around could only cause confusion.
(Assignee)

Comment 1

7 years ago
I filed <http://www.w3.org/Bugs/Public/show_bug.cgi?id=11439> to get the properties on LSProgressEvent specified. Once that's done, we can kill LSProgressEvent too.
(Assignee)

Comment 2

7 years ago
Created attachment 494666 [details] [diff] [review]
Patch v1
Attachment #494666 - Flags: review?(jonas)
This is for after Firefox 4, right?
(Assignee)

Comment 4

7 years ago
Yeah.
Target Milestone: --- → Future
The one thing we could do for FF4 is to add warnings to progress events when accessing the LSProgressEvent properties. Then maybe we can deprecate them in the future.
(Assignee)

Comment 6

7 years ago
We could, but should we? I've skimmed over the code, and it doesn't seem like we expose the contents in another way. I'm not a big fan of telling people they can't use a feature if there's nothing they can migrate to. Happy to be proved wrong, though.

Comment 7

7 years ago
(In reply to comment #6)
> We could, but should we? I've skimmed over the code, and it doesn't seem like
> we expose the contents in another way. I'm not a big fan of telling people they
> can't use a feature if there's nothing they can migrate to. Happy to be proved
> wrong, though.
We have progress events for XHR, and also for XHR.upload.
Currently during upload the properties of LSProgressEvent report also the header size, but that and the difference in multipart XHR handling are the only differences, IIRC.
IMO the implementation of LSProgressEvent properties is a bit strange,
and should be removed eventually. So we could start to warn about using
them.
(Assignee)

Updated

7 years ago
Depends on: 616672
(Assignee)

Updated

7 years ago
Depends on: 610267
Whiteboard: [needs landing]
(Assignee)

Comment 8

7 years ago
Created attachment 522214 [details] [diff] [review]
Patch for checkin
Attachment #494666 - Attachment is obsolete: true
(Assignee)

Updated

7 years ago
Keywords: checkin-needed
Whiteboard: [needs landing]

Updated

7 years ago
Keywords: checkin-needed

Comment 10

7 years ago
http://hg.mozilla.org/mozilla-central/rev/286a6d0c1f40
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Whiteboard: fixed-in-cedar
Target Milestone: Future → mozilla2.2
Component: DOM: Other → DOM
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.