Open Bug 1659927 Opened 4 years ago Updated 3 years ago

Content area does not get focus after drag & drop a html file to about:newtab page from Explorer

Categories

(Firefox :: Tabbed Browser, defect, P2)

80 Branch
Desktop
Windows 10
defect

Tracking

()

Tracking Status
firefox-esr68 --- unaffected
firefox-esr78 --- unaffected
firefox79 --- unaffected
firefox80 --- wontfix
firefox81 --- wontfix
firefox82 --- fix-optional

People

(Reporter: alice0775, Unassigned)

References

(Regression)

Details

(Keywords: nightly-community, regression, ux-consistency)

Reproducible : always

Steps To Reproduce:

  1. Open New Tab Page or Default Home
    --- Observe address bar gets focus as expected
  2. Drag and drop a html file to blank area of the New Tab Page from Explorer
  3. Click on Browser Title bar or Task button of Firefox in Windows taskbar so that Brower window will be topmost.

Actual Results:
Page loaded as expected.
However, Content area does not get focus. Address bar is still focused (i.e, blinking caret in the address bar).
So, Content area would not scroll with key board unless click the content area.

Expected Results:
Content area should get focus.

Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=cc6516a63bb5500f1594ea675766f418dc4bed23&tochange=1628b650e8fb6437de6f0146d993b119d4e2cd21

Component: Address Bar → New Tab Page
Severity: -- → S3
Component: New Tab Page → Tabbed Browser
Priority: -- → P2

Regression from a recent landing related to focus. Is this something we want to fix?

Flags: needinfo?(kmadan)

(In reply to Jim Mathies [:jimm] from comment #1)

Is this something we want to fix?

Yeah, probably. I don't think it's high priority just because we make it clear that chrome is focused instead of content (since the address bar is enlarged/highlighted), and so anyone that runs into this will naturally just click the content area before attempting to interact with the page.

I'll assign myself, but I'm unsure how soon I'll get to this.

Flags: needinfo?(kmadan)
Assignee: nobody → kmadan

Clearing assignee because Kashav is no longer at Mozilla.

Assignee: kshvmdn+bmo → nobody
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.