Closed Bug 1395114 Opened 5 years ago Closed 5 years ago

Remove nsIUnicharStreamLoader

Categories

(Core :: Networking, enhancement, P5)

Product:
Core
Component:
Networking
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla61
Tracking Flags:
Tracking Status
firefox61 --- fixed

People

(Reporter: hsivonen, Assigned: hsivonen)

References

Details

(Whiteboard: [necko-would-take])

Attachments

(1 file)

Bug 1395114 - Remove nsIUnicharStreamLoader.
59 bytes, text/x-review-board-request
emilio
: review+
michal
: review+
Details 
We should remove nsIUnicharStreamLoader once the old style system is no longer around to use it.
No longer depends on: stylo-everywhere
We're still using Gecko's CSS loader to load servo stylesheets, so not sure removing the old style system changes the picture here.
Depends on: 1395118
(In reply to Emilio Cobos Álvarez [:emilio] from comment #1)
> We're still using Gecko's CSS loader to load servo stylesheets, so not sure
> removing the old style system changes the picture here.

I'm removing nsIUnicharStreamLoader usage in the Stylo case in bug 1354989.
Whiteboard: [necko-would-take]
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P5
Assignee: nobody → hsivonen
Status: NEW → ASSIGNED
Comment on attachment 8962281 [details]
Bug 1395114 - Remove nsIUnicharStreamLoader.

https://reviewboard.mozilla.org/r/231142/#review236616
Attachment #8962281 - Flags: review?(michal.novotny) → review+
Comment on attachment 8962281 [details]
Bug 1395114 - Remove nsIUnicharStreamLoader.

https://reviewboard.mozilla.org/r/231142/#review236724
Attachment #8962281 - Flags: review?(emilio) → review+
Pushed by hsivonen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/80a1cfc4f069
Remove nsIUnicharStreamLoader. r=emilio,michal
https://hg.mozilla.org/mozilla-central/rev/80a1cfc4f069
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox61: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla61
You need to log in before you can comment on or make changes to this bug.