-
Notifications
You must be signed in to change notification settings - Fork 22.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fold LinkStyle (a mixin) into its inheriting interfaces #5669
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a mention of LinkStyle
in https://developer.mozilla.org/en-US/docs/Web/API/SVGStyleElement . I think we should add the sheet
method here too (like in HTMLStyleElement
, HTMLLinkElement
, ProcessingInstruction
).
I've not double checked, but I think doing rg LinkStyle *
in api/
to check that every mentions of LinkStyle
have been dealt with may be useful. (rg
is a recursive version of grep
).
Very happy to see LinkStyle
going away.
Preview URLs
FlawsURL:
URL:
URL:
URL:
URL:
URL:
URL:
External URLsURL: No new external URLs URL: No new external URLs URL: No new external URLs URL:
URL: No new external URLs URL: No new external URLs URL: No new external URLs (this comment was updated 2021-06-08 13:22:38.053554) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @vinyldarkscratch 👋 this looks awesome 😎
Seems tests are failing on redirect because the sheet
property page doesn't exist. Basically it seems it just never got written... I think possibly for the moment we just redirect any Link/sheet urls to Web/API/HTMLLinkElement
I've added a suggestion, but happy to have a better one :)
@@ -115,7 +115,7 @@ <h4 id="WebRTC">WebRTC</h4> | |||
<h4 id="New_APIs">New APIs</h4> | |||
|
|||
<ul> | |||
<li>In SVG, the {{domxref("SVGStyleElement")}} interface now implements the {{domxref("LinkStyle")}} mixin ){{bug(1239128)}}.</li> | |||
<li>In SVG, the {{domxref("SVGStyleElement")}} interface now implements the {{domxref("SVGStyleElement.sheet")}} member ){{bug(1239128)}}.</li> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In release notes, let's not change any wording, but just remove the domxref and use just <code>
instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree!
@@ -98,7 +98,7 @@ <h2 id="Specifications">Specifications</h2> | |||
<tr> | |||
<td>{{SpecName('DOM2 HTML', 'html.html#ID-35143001', 'HTMLLinkElement')}}</td> | |||
<td>{{Spec2('DOM2 HTML')}}</td> | |||
<td>Added a second inheritence, the {{domxref("LinkStyle")}} interface.</td> | |||
<td>Added a second inheritence, the LinkStyle mixin, exposing the {{domxref("HTMLLinkElement.sheet")}} member.</td> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In spec tables I would also leave the text unchanged, just replace the domxref.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good apart from one small nit.
@Rumyra might you be able to review this? If you agree with my suggestion, just applying it an merging should be OK. |
Co-authored-by: Philip Jägenstedt <philip@foolip.org>
Approved @foolip - I'm unsure of the status of the two unresolved conversations above - are we ok to merge? Happy to do so :) |
@Rumyra those issues have been resolved. I'm not sure why there's no "resolve" button, but they're outdated at any rate. |
@foolip weirdly I do have a resolve button hence the query 🤷🏻♀️ anyways thank you 🙏 all merged |
This PR removes the pages for the
LinkStyle
mixin and remaps the references of its only member (sheet
) to the individual interfaces. There is no page already in place for the member, unfortunately, so the link will remain a 404 for the time being.Note: this is my first PR for the MDN content (though not my first content edit altogether), and especially my first attempt at a change like this. Please let me know if I missed anything!
Corresponding BCD PR: mdn/browser-compat-data#10724