Closed Bug 1355363 Opened 7 years ago Closed 7 years ago

The title attibute of a link doesn't contain all the info it should

Categories

(Developer Documentation Graveyard :: General, enhancement, P5)

All
Other
enhancement

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: regspam, Unassigned)

References

()

Details

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

Hover the mouse over the underlined "CORS-safelisted response-header". The text "CORS-safelisted response-header: A simple response header (or a CORS-safelisted response header) is an HTTP header that is one of the following:" appears, as specified in the title attribute of the corresponding <a> element, which is, obviously, only a part of what should be in there.
There's only so long you really want those tooltips to get. They're meant to be simple previews, not full-on documentation. That said, you're right that that terminates abruptly. See if you like it better now. You may need to shift-refresh the page the link is on to pick up the updated text.

If you don't feel this is resolved, please re-open this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(regspam)
Resolution: --- → FIXED
Thanks for the response. Sorry, I specified a wrong URL in the "Page to Update" field when reporting the bug, it should be 
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type (corrected it now), not https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options.

I can't see any changes in the title info of "CORS-safelisted response-header" on https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type - am I right in thinking that you updated the site code so that "CORS-safelisted response-header" (as well as all other links of that type) is now clickable and points to https://developer.mozilla.org/en-US/docs/Glossary/Simple_response_header?
Status: RESOLVED → VERIFIED
Flags: needinfo?(regspam)
You need to log in before you can comment on or make changes to this bug.