Closed
Bug 25185
Opened 25 years ago
Closed 25 years ago
Cannot open url with #
Categories
(Core Graveyard :: Tracking, defect, P3)
Tracking
(Not tracked)
M14
People
(Reporter: mktakaha, Assigned: andreas.otte)
References
()
Details
(Keywords: testcase, Whiteboard: [PDT+] ikibbles@bigfoot.com)
Attachments
(1 file)
I can view page below
http://homepage1.nifty.com/hobbit/child/jitenutf/ura.html
but I cannot view page with url attached by # such as below
http://homepage1.nifty.com/hobbit/child/jitenutf/ura.html#auel
Comment 1•25 years ago
|
||
What happens is that the display area becomes "transparent", i.e. contains
whatever was last in that area of screen, but the surrounding stuff like the URL
bar remains responsive and you can correct the URL. If you load the page and
then append the # bit to the URL and reload, it moves down the page fine. It's
only on first visiting that there's a problem.
Using M13 on Win32.
Gerv
Severity: normal → critical
Whiteboard: [MAKINGTEST] ikibbles@bigfoot.com → [TESTCASE] ikibbles@bigfoot.com
Assignee | ||
Comment 5•25 years ago
|
||
I think it's a dup of 24642. Urlparsing seems fine, I'm guessing it's a webshell
thing in trying to detect if the document was already loaded and jumping to the
anchor only.
I'm getting this messages on the console:
FindShortcut:
in='http://homepage1.nifty.com/hobbit/child/jitenutf/ura.html#auel' out='null'
Error loading URL http://homepage1.nifty.com/hobbit/child/jitenutf/ura.html#auel
Document: Done (10.196 secs)
Error loading URL http://homepage1.nifty.com/hobbit/child/jitenutf/ura.html#auel
Document: Done (0.109 secs)
Putting on PDT+ radar for beta1.
Keywords: testcase
Whiteboard: [TESTCASE] ikibbles@bigfoot.com → [PDT+] ikibbles@bigfoot.com
Assignee | ||
Comment 7•25 years ago
|
||
*** This bug has been marked as a duplicate of 24642 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 8•25 years ago
|
||
I am testing today's Mac commercial bits from 2pm (2nd round of builds).
I disagree that this is a duplicate of that other bug since the other bug is
really about a crasher. I have tested with the following url and I did jump to
the proper location within this url:
http://www.mozilla.org/editor/ui_specs/OpenPageDialogs.html#OpenPage
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•