Closed
Bug 1298625
Opened 8 years ago
Closed 7 years ago
Date and Time picker tutorial link on <input type="date"> page goes to Buttons tutorial instead.
Categories
(Developer Documentation Graveyard :: HTML, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: csanchez2237, Unassigned)
References
()
Details
(Whiteboard: [specification][type:bug])
What did you do?
================
I clicked on the link
What happened?
==============
I ended up at the buttons tutorial.
What should have happened?
==========================
I should have ended up at the Date and Time Picker tutorial (which is farther down the page).
Is there anything else we should know?
======================================
Updated•8 years ago
|
Component: Design → HTML
Product: Mozilla Developer Network → Developer Documentation
Comment 1•8 years ago
|
||
Hello,
I can reproduce this with IE11 and Chrome 52, but not with Firefox 48 (all on Win7 pro).
specially on Google Chrome every click on the link
https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Forms/The_native_form_widgets#Date_and_time_picker
will move to an different part of the site.
can you please give us some more information about your Browser Version and System?
Flags: needinfo?(csanchez2237)
Reporter | ||
Comment 2•8 years ago
|
||
I'm using Chrome 53 and Windows 10. Is that everything you needed?
Comment 3•8 years ago
|
||
Thank you for your feedback, so i was able to reproduce again.
it looks like it is an error on Google Chrome and not the page.
first the page scrolls to the correct anchor and after, it jumps back up the page.
I can't find a command for this jump in the page code (maybe the menu on the right?)
there are some open bugs on google chrome about the anchor topic, but i was not able to find a specific one about this problem.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(csanchez2237)
Updated•8 years ago
|
Blocks: input-type-docs
Comment 4•7 years ago
|
||
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•