Closed Bug 1883316 Opened 4 months ago Closed 4 months ago

Browsing to a fragment must automatically open details elements as needed

Categories

(Core :: DOM: Navigation, defect)

Firefox 123
x86_64
Windows 10
defect

Tracking

()

RESOLVED DUPLICATE of bug 1724299

People

(Reporter: org.mozilla.bugzilla.gv9e0j41, Unassigned)

Details

Attachments

(1 file)

Attached file test.html

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0

Steps to reproduce:

The following are 2 alternative ways to reproduce, and I expect both of them to work:

a) Open the file, scroll down, click "foo" (i.e. navigate to the fragment via a link)
b) Append #foo in the address bar and hit Enter (i.e. navigate to the fragment directly)

Actual results:

Nothing

Expected results:

The details elements are opened and the page starts at the paragraph with the text "foo". (If this is unclear: I expect the same behavior as Edge)

I was able to reproduce the issue on Win10x64 using Firefox build 123.0(20240213221259).
If I open the attached link test.html, go to the bottom of it where the foo link is, and I press on it I am redirected to the expanded foo from the top this is the behavior on both Chrome and Edge, while on Firefox foo ii not expanded. There is a different behavior between FF and Chrome/Edge.
Marking issue as New. If component is not correct please update. Thank you.

Status: UNCONFIRMED → NEW
Has STR: --- → yes
Component: Untriaged → General
Ever confirmed: true
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64

:sefeng Can reproduce this on a Mac as well - unsure what the intended behavior is as it differs between browsers. Could you take a look to determine if this is something that should be fixed?

Component: General → DOM: Navigation
Flags: needinfo?(sefeng)
Product: Firefox → Core

So Safari also behaves the same as Firefox, it doesn't open the detail.

I think the spec should define this so this inconsistent behaviour can be fixed. Not sure if this is defined or known already.

Simon, do you think we should file a spec issue for this?

Flags: needinfo?(sefeng) → needinfo?(zcorpan)

ah thanks!

Status: NEW → RESOLVED
Closed: 4 months ago
Duplicate of bug: 1724299
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: