Closed
Bug 1198896
Opened 9 years ago
Closed 9 years ago
Allow <a> tags in specification description
Categories
(developer.mozilla.org Graveyard :: BrowserCompat, defect)
developer.mozilla.org Graveyard
BrowserCompat
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jwhitlock, Assigned: jwhitlock)
References
()
Details
(Whiteboard: [bc:infra])
What did you do? ================ With the new importer from bug 1171957: 1. Go to https://browsercompat.herokuapp.com/importer/754 (importer page for https://developer.mozilla.org/en-US/docs/Web/CSS/image) 2. Press "Reset" button What happened? ============== Get warning "HTML element <a> (but not wrapped content) was removed." What should have happened? ========================== <a> tag should have been allowed, with MDN local links converted to absolute links Is there anything else we should know? ====================================== <a> tags appear 61 times in specification descriptions.
|
Assignee | |
Updated•9 years ago
|
|
|
Assignee | |
Updated•9 years ago
|
Assignee: nobody → jwhitlock
|
||
Comment 1•9 years ago
|
||
Commits pushed to master at https://github.com/mdn/browsercompat https://github.com/mdn/browsercompat/commit/77ad0a0213ae40e4ea9db1dbbd78101dd053c328 bug 1198896 - Convert relative <a> links https://github.com/mdn/browsercompat/commit/94ec8dce12c22d6b7ad474e23246fcb882ad3ec1 fix bug 1198896 - Allow <a> tags in spec. desc. https://github.com/mdn/browsercompat/commit/95ddb89a9c167088c0898c1ce06d6d4276a1e3f1 Merge pull request #44 from mdn/improve_a_1181140 bug 1198896 - Improve handling of <a> tags +r groovecoder
|
|
||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
|
||
Updated•8 years ago
|
Keywords: in-triage
OS: Other → All
Summary: [CompatData][Importer] Allow <a> tags in specification description → Allow <a> tags in specification description
Whiteboard: [specification][type:bug] → [bc:infra]
|
||
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•