Closed Bug 1626507 Opened 5 years ago Closed 4 years ago

Remove the document channel exception for about:newtab

Categories

(Core :: DOM: Navigation, task, P3)

task

Tracking

()

RESOLVED FIXED
mozilla80
Fission Milestone M6a
Tracking Status
firefox80 --- fixed

People

(Reporter: pbone, Assigned: pbone)

References

(Blocks 1 open bug)

Details

(Whiteboard: [7/14] ETA: 2020-07-17)

Attachments

(5 files)

In Bug 1597154 I added an exception for about:newtab, this should be removed, but doing so breaks browser/components/uitour/test/browser_UITour_showNewTab.js where the address bar isn't focused for the new tab. This should be fixed and the exception can be removed.

Fission Milestone: --- → M6
Depends on: 1597154
Assignee: nobody → pbone
Status: NEW → ASSIGNED

Tracking for Fission M6a because Paul said he wanted to clean up this code soon.

Severity: normal → S3
Fission Milestone: M6 → M6a
Priority: -- → P3
See Also: → 1634272

This patch removes the excemptions for about:newtab, about:home and
about:blank.

When we switch processes using session restore we sometimes focus the
content area. We mustn't do this if the uri is undefined, this can happen
for some of these pages and we expect the address bar to be focused instead.

Pushed by pbone@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d2e886102c03 Remove documentchannel exceptions r=mattwoodrow https://hg.mozilla.org/integration/autoland/rev/92117ff66bda Update comment since code has moved r=mattwoodrow
Attachment #9157862 - Attachment description: Bug 1626507 - Remove documentchannel exceptions r=mattwoodrow → Bug 1626507 - pt 1. Remove documentchannel exceptions r=mattwoodrow
Attachment #9158422 - Attachment description: Bug 1626507 - Update comment since code has moved r=mattwoodrow → Bug 1626507 - pt 2. Update comment since code has moved r=mattwoodrow

Two tests in this file had the same name, give this one a more specific name
so that console output is easier to follow.

Depends on D80594

Due to changes in about:newtab somehow the preferences code is getting
initialised before the call to openPreferencesViaOpenPreferencesAPI().
Update this code to work when preferences is already initialised.

Depends on D81066

Flags: needinfo?(pbone)

I said in the meeting today that this is blocked on fixing BC preservation, it isn't. The reason it can't land is that there's still test failures to fix:

https://treeherder.mozilla.org/#/jobs?repo=try&selectedTaskRun=KoHNcnIpTkOTn-14mA-aEA.0&revision=f7a47df5aab71f54befed4bf4ddceaad89f68f88

Paul, please provide an ETA for this in the whiteboard field.

Flags: needinfo?(pbone)
Whiteboard: [7/14] ETA: ?
Flags: needinfo?(pbone)
Whiteboard: [7/14] ETA: ? → [7/14] ETA: 2020-07-17
Depends on: 1596738
Pushed by pbone@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/641595f11928 pt 1. Remove documentchannel exceptions r=mattwoodrow https://hg.mozilla.org/integration/autoland/rev/2a0d4fe417c0 pt 2. Update comment since code has moved r=mattwoodrow https://hg.mozilla.org/integration/autoland/rev/521431bda0c7 pt 3. Rename a test to make it distinct from other tests r=preferences-reviewers,jaws https://hg.mozilla.org/integration/autoland/rev/b351d22f9100 pt 4. Fix openPreferencesViaOpenPreferencesAPI r=preferences-reviewers,jaws

I didn't see this reviewer comment on my patch until after I'd clicked land.
Sorry.

Pushed by gijskruitbosch@gmail.com: https://hg.mozilla.org/integration/autoland/rev/89354b22efcd pt 5. Remove duplicate call to openPreferences r=Gijs,preferences-reviewers
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: