Closed Bug 1448058 Opened 3 years ago Closed 3 years ago

Remove nsIMutable from URI implementations

Categories

(Core :: Networking, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla62
Tracking Status
firefox61 --- wontfix
firefox62 --- fixed

People

(Reporter: valentin, Assigned: valentin)

References

(Regressed 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

Since URI implementations are now immutable, there is no need for objects to implement the nsIMutable interface.
Priority: -- → P3
Duplicate of this bug: 1448327
Comment on attachment 8973988 [details]
Bug 1448058 - Remove nsIMutable from URI implementations

https://reviewboard.mozilla.org/r/242324/#review248554
Attachment #8973988 - Flags: review?(honzab.moz) → review+
We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again.

hg error in cmd: hg rebase -s 10f2ac96468ddbaf23a3090f6441a3fb46d9743e -d bd5d3654b01e: rebasing 462834:10f2ac96468d "Bug 1448058 - Remove nsIMutable from URI implementations r=mayhemer" (tip)
merging caps/ContentPrincipal.cpp
merging chrome/nsChromeProtocolHandler.cpp
merging docshell/base/nsDocShell.cpp
merging dom/base/nsContentUtils.cpp
merging dom/base/nsDocument.cpp
merging dom/base/nsImageLoadingContent.cpp
merging dom/base/nsObjectLoadingContent.cpp
merging dom/html/nsHTMLDocument.cpp
merging netwerk/base/nsNetUtil.cpp
merging netwerk/base/nsNetUtil.h
merging netwerk/base/nsSimpleURI.cpp
merging netwerk/base/nsStandardURL.cpp
warning: conflicts while merging netwerk/base/nsNetUtil.cpp! (edit, then use 'hg resolve --mark')
unresolved conflicts (see hg resolve, then hg rebase --continue)
Pushed by valentin.gosu@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/c10e876269a9
Remove nsIMutable from URI implementations r=mayhemer
https://hg.mozilla.org/mozilla-central/rev/c10e876269a9
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
Regressions: 1570786
You need to log in before you can comment on or make changes to this bug.