-
Notifications
You must be signed in to change notification settings - Fork 36
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
Add support for the <wpt> element #90
Conversation
645ff87
to
05e77f9
Compare
src/wattsi.pas
Outdated
WPTOutput.Add('<li class=wpt-test>'); | ||
WPTOutput.Add('<a href="https://wpt.fyi/results' | ||
+ WPTPath + '">' + WPTFilename + '</a>'); | ||
WPTOutput.Add('<a href="http://web-platform-tests.live' |
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.
This should have similar logic as
https://github.com/web-platform-tests/wpt.fyi/blob/master/webapp/components/test-runs.html#L74
for http vs https.
src/wattsi.pas
Outdated
@@ -2015,6 +2051,41 @@ procedure Save(const Document: TDocument; const FileName: AnsiString; const InSp | |||
if (Current is TElement) then | |||
begin | |||
Element := TElement(Current); | |||
// TODO: Move the styles below to https://resources.whatwg.org/spec.css or |
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.
Address this
This change adds support for generating output from the `<wpt>` element, as documented at https://tabatkins.github.io/bikeshed/#wpt-element) and discussed at speced/bikeshed#1116. Specifically, this change causes lists of tests in `<wpt>` elements from the source to generate TESTS sections in the spec output, with links to corresponding https://github.com/web-platform-tests/wpt, https://wpt.fyi and https://web-platform-tests.live URLs for the listed tests. The change by design intentionally doesn’t provide the following `<wpt>`-related features: - Doesn’t verify that each test listed in a `<wpt>` element actually exists in https://github.com/web-platform-tests/wpt/ - Doesn’t verify that every single test file that exists in the https://github.com/web-platform-tests/wpt/tree/master/html tree is listed in a `<wpt>` element somewhere in the spec source. Fixes #87
014ab4d
to
1649eff
Compare
1649eff
to
cb86e15
Compare
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.
LGTM except for the TODO
OK, da2eea9 removes the embedded styles, and whatwg/whatwg.org#230 moves them to https://resources.whatwg.org/standard.css |
The outputted HTML here differs from what I'm seeing in e.g. the bottom of https://quirks.spec.whatwg.org/#the-hashless-hex-color-quirk , which I assume is the HTML produced by Bikeshed. Among other things, this means we can't merge whatwg/whatwg.org#230 because then those styles would mess up quirks.whatwg.org. Probably we should align? :-/ |
Can we omit these from review draft mode? |
I think we already have it doing that — see 6bb32df. Is that not working as expected? |
OK, to fix that for now, I can update the stylesheet patch to instead use the class name Would that be sufficient for now? Long term, I think @tabatkins has already said he’s supportive of adding support to Bikeshed for also styling the But for right now, if I just change the class name, that avoids the current conflict. So please lemme know if that would resolve it satisfactorily for the time being. |
Agreed, let's just change the class name. I'll try doing that and merging myself. We should come up with a nice long-term plan for the markup and CSS for all of this. See whatwg/meta#117 for my thoughts there. But let's get it all in and working first :). |
See whatwg/wattsi#90. Eventually we may use similar styles for <wpt> annotations in specs besides HTML; for now they are using Bikeshed's built-in styles. Unification is tracked at whatwg/meta#117.
This change adds support for generating output from the
<wpt>
element, as documented at https://tabatkins.github.io/bikeshed/#wpt-element) and discussed at speced/bikeshed#1116.Specifically, this change causes lists of tests in
<wpt>
elements from the source to generate TESTS sections in the spec output, with links to corresponding https://github.com/web-platform-tests/wpt, https://wpt.fyi and https://web-platform-tests.live URLs for the listed tests.The change by design intentionally doesn’t provide the following
<wpt>
-related features:Doesn’t verify that each test listed in a
<wpt>
element actually exists in https://github.com/web-platform-tests/wpt/Doesn’t verify that every single test file that exists in the https://github.com/web-platform-tests/wpt/tree/master/html tree is listed in a
<wpt>
element somewhere in the spec source.Fixes #87