Note: There are a few cases of duplicates in user autocompletion which are being worked on.

Revert to old View Source back end for Firefox 10

RESOLVED FIXED in Firefox 10

Status

()

Core
HTML: Parser
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: hsivonen, Assigned: hsivonen)

Tracking

({dev-doc-complete})

10 Branch
mozilla10
dev-doc-complete
Points:
---

Firefox Tracking Flags

(firefox10 fixed)

Details

(Whiteboard: [qa-])

Attachments

(1 attachment)

The new View Source implementation landed so that it went into Aurora with the Firefox 10 release train. Afterwards, regressions were fixed on trunk (for Firefox 11). The choice whether to land the fixes on a branch or whether to go back to the old code on the branch is a call for the release drivers, but this bug is a placeholder for going back to the old code on the branch.
Created attachment 581228 [details] [diff] [review]
Go back to using the old View Source back end

The #defines I had put in place didn't support the configuration where the new parser is used for non-View Source plain text processing but the old parser is used for all kind of View Source. That's why I removed the #defines and hard-coded the desired behavior for this branch-only patch. Note that nsHtml5Module::sEnabled is always true anyway.
Attachment #581228 - Flags: review?(bugs)

Comment 2

6 years ago
Just curious, has there been any major problems in the new view source?
I don't recall any. All the patches I've reviewed should just go to Aurora.

Comment 3

6 years ago
Comment on attachment 581228 [details] [diff] [review]
Go back to using the old View Source back end


>   waitForExplicitFinish();
>   openViewSourceWindow(source, function(aWindow) {
>     let gBrowser = aWindow.gBrowser;
> 
>-    todo(gBrowser.contentDocument.title == source, "Correct document title");
>+    ok(gBrowser.contentDocument.title == source, "Correct document title");
Or is this still something to fix in the new view source. Doesn't look too hard.
Attachment #581228 - Flags: review?(bugs) → review+
(In reply to Olli Pettay [:smaug] from comment #2)
> Just curious, has there been any major problems in the new view source?
> I don't recall any. All the patches I've reviewed should just go to Aurora.

Nothing that I'd consider major, but there's one unfixed minor regression still: bug 710142. (I agree that technically the fixes could be landed on Aurora. And the last unfixed regression could probably be fixed on Beta if it doesn't get fixed before Dec 20th.)

(In reply to Olli Pettay [:smaug] from comment #3)
> Comment on attachment 581228 [details] [diff] [review]
> Go back to using the old View Source back end
> 
> 
> >   waitForExplicitFinish();
> >   openViewSourceWindow(source, function(aWindow) {
> >     let gBrowser = aWindow.gBrowser;
> > 
> >-    todo(gBrowser.contentDocument.title == source, "Correct document title");
> >+    ok(gBrowser.contentDocument.title == source, "Correct document title");
> Or is this still something to fix in the new view source. Doesn't look too
> hard.

This is something that's fixed in the new View Source on trunk but the patch landed after the Aurora uplift.

Thank you for the r+.
Comment on attachment 581228 [details] [diff] [review]
Go back to using the old View Source back end

(This comment has been posted on all the bugs mentioned in this comment, except bug 710142, so that the release drivers see it regardless of the order in which they process approval requests.)

The new View Source implementation landed before Firefox 10 moved to Aurora. Afterwards, a bunch of regressions were identified. Many of the regression fixes didn't land before Firefox 10 moved to Aurora but they have now been fixed on trunk except for bug 710142.

To avoid shipping with regressions, we either need to land all the regression fixes on Aurora for Firefox 10 (followed by a fix for bug 710142 in Beta if it doesn't make it before Dec 20th) or switch back to the old View Source implementation on Aurora. The new View Source implementation provides much better diagnostics for Web developers than the old View Source implementation.

So I'd like to ask the release drivers to either approve bug 535530, bug 699356, bug 699365, bug 700034, bug 700361, bug 703965, bug 704667 and bug 705473 plus bug 695640, which is a non-regression tweak, or to approve bug 710175 for reverting to the old View Source implementation for Firefox 10.
Attachment #581228 - Flags: approval-mozilla-aurora?
(In reply to Henri Sivonen (:hsivonen) from comment #5)
> So I'd like to ask the release drivers to either approve bug 535530, bug
> 699356, bug 699365, bug 700034, bug 700361, bug 703965, bug 704667 and bug
> 705473 plus bug 695640, which is a non-regression tweak, or to approve bug
> 710175 for reverting to the old View Source implementation for Firefox 10.

Given the number of patches, I think we should revert to the old version on Aurora (i.e. take this patch). We shouldn't generally be doing bug fixing on Aurora (we have in the past for a small number of minor fixes, but all of those bugs combined doesn't seem "small" to me).

Comment 7

6 years ago
Comment on attachment 581228 [details] [diff] [review]
Go back to using the old View Source back end

[triage comment]
We decided to back out the new view source parser (which is this bug!) rather than take the fixups for Firefox 10.

Approved for Aurora, please land ASAP.
Attachment #581228 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
https://hg.mozilla.org/releases/mozilla-aurora/rev/fbda7c5fe59c
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED

Comment 9

6 years ago
Documentation for bug 482921 probably needs to change.
Keywords: dev-doc-needed
(In reply to j.j. from comment #9)
> Documentation for bug 482921 probably needs to change.

MDN edited accordingly.
Keywords: dev-doc-needed → dev-doc-complete
status-firefox10: --- → fixed
Target Milestone: --- → mozilla10
Marking qa- as I don't think this is something QA needs to verify. Please mark qa+ if this is not the case.
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.