Submissions/opera microdata #24
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I need the manifest. |
|
I think these have been reviewed when Mozilla implemented microdata. So, if the manifest is put back, I guess we can merge this. |
|
The manifest did get lost, so I added it back: 86dd482 |
jugglinmike
pushed a commit
to bocoup/wpt
that referenced
this pull request
Apr 11, 2017
…_enum_support Added support for enum in idlharness.js
jgraham
added a commit
that referenced
this pull request
Apr 13, 2017
Seems this example doesn't work without the status
jgraham
added a commit
that referenced
this pull request
Apr 13, 2017
Add support for filtering displayed test results.
jgraham
added a commit
that referenced
this pull request
Apr 21, 2017
Move to a new way of overriding the server url that also works for templates
AutomatedTester
referenced
this pull request
in AutomatedTester/web-platform-tests
Dec 1, 2017
stephenmcgruer
added a commit
that referenced
this pull request
Mar 2, 2021
…db3d29db4 9db3d29db4 Bump version number to reflect functional changes (#25) c6aea56f8b Stop wrapping os.popen3 (#24) 353b4aaf8a Give up expecting echo_client to be unicode safe (#23) 9ae2b3c90b Make tests work with python 2 on Windows (#20) e894c1b2ad Update the URL in setup.py (#19) f76e23c094 Fix incorrect use of "is" for integer comparison (#21) 3ab411d97f Fix version comparisons (#22) git-subtree-dir: tools/third_party/pywebsocket3 git-subtree-split: 9db3d29db4f3e3efb1722c0210bc88500ab00611
stephenmcgruer
added a commit
that referenced
this pull request
Mar 2, 2021
…db3d29db4 9db3d29db4 Bump version number to reflect functional changes (#25) c6aea56f8b Stop wrapping os.popen3 (#24) 353b4aaf8a Give up expecting echo_client to be unicode safe (#23) 9ae2b3c90b Make tests work with python 2 on Windows (#20) e894c1b2ad Update the URL in setup.py (#19) f76e23c094 Fix incorrect use of "is" for integer comparison (#21) 3ab411d97f Fix version comparisons (#22) git-subtree-dir: tools/third_party/pywebsocket3 git-subtree-split: 9db3d29db4f3e3efb1722c0210bc88500ab00611
chromium-wpt-export-bot
pushed a commit
that referenced
this pull request
Aug 9, 2021
Currently, Blink does not implement complete spec rules for determining the form of an <mo> element [1]. It just checks whether there are a nodes before or after the <mo> to calculate whether the form is prefix, infix or postfix. Once we support embellished operators [2], this will require a bigger code refactoring. Meanwhile, this CL fixes the common case where the <mo> has non-element nodes before or after it that must be ignored for the calculation of the form. This is visible on test #24 from Mozilla's MathML test [3] where the prefix/postfix form of "|" are stretchy but the non-stretchy infix form is used because of whitespace text nodes. Bug: 6606, 1121113, 1124301 [1] https://bugs.chromium.org/p/chromium/issues/detail?id=1121113 [2] https://bugs.chromium.org/p/chromium/issues/detail?id=1124298 [3] https://fred-wang.github.io/MathFonts/mozilla_mathml_test/ Change-Id: I42ff3b821d2f2da201b1ff4a4612a8d5756486a8
chromium-wpt-export-bot
pushed a commit
that referenced
this pull request
Aug 10, 2021
Currently, Blink does not implement complete spec rules for determining the form of an <mo> element [1]. It just checks whether there are a nodes before or after the <mo> to calculate whether the form is prefix, infix or postfix. Once we support embellished operators [2], this will require a bigger code refactoring. Meanwhile, this CL fixes the common case where the <mo> has non-element nodes before or after it that must be ignored for the calculation of the form. This is visible on test #24 from Mozilla's MathML test [3] where the prefix/postfix form of "|" are stretchy but the non-stretchy infix form is used because of whitespace text nodes. Bug: 6606, 1121113, 1124301 [1] https://bugs.chromium.org/p/chromium/issues/detail?id=1121113 [2] https://bugs.chromium.org/p/chromium/issues/detail?id=1124298 [3] https://fred-wang.github.io/MathFonts/mozilla_mathml_test/ Change-Id: I42ff3b821d2f2da201b1ff4a4612a8d5756486a8
chromium-wpt-export-bot
pushed a commit
that referenced
this pull request
Aug 10, 2021
Currently, Blink does not implement complete spec rules for determining the form of an <mo> element [1]. It just checks whether there are a nodes before or after the <mo> to calculate whether the form is prefix, infix or postfix. Once we support embellished operators [2], this will require a bigger code refactoring. Meanwhile, this CL fixes the common case where the <mo> has non-element nodes before or after it that must be ignored for the calculation of the form. This is visible on test #24 from Mozilla's MathML test [3] where the prefix/postfix form of "|" are stretchy but the non-stretchy infix form is used because of whitespace text nodes. Bug: 6606, 1121113, 1124301 [1] https://bugs.chromium.org/p/chromium/issues/detail?id=1121113 [2] https://bugs.chromium.org/p/chromium/issues/detail?id=1124298 [3] https://fred-wang.github.io/MathFonts/mozilla_mathml_test/ Change-Id: I42ff3b821d2f2da201b1ff4a4612a8d5756486a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3081881 Commit-Queue: Frédéric Wang <[email protected]> Reviewed-by: Rob Buis <[email protected]> Cr-Commit-Position: refs/heads/master@{#910252}
chromium-wpt-export-bot
pushed a commit
that referenced
this pull request
Aug 10, 2021
Currently, Blink does not implement complete spec rules for determining the form of an <mo> element [1]. It just checks whether there are a nodes before or after the <mo> to calculate whether the form is prefix, infix or postfix. Once we support embellished operators [2], this will require a bigger code refactoring. Meanwhile, this CL fixes the common case where the <mo> has non-element nodes before or after it that must be ignored for the calculation of the form. This is visible on test #24 from Mozilla's MathML test [3] where the prefix/postfix form of "|" are stretchy but the non-stretchy infix form is used because of whitespace text nodes. Bug: 6606, 1121113, 1124301 [1] https://bugs.chromium.org/p/chromium/issues/detail?id=1121113 [2] https://bugs.chromium.org/p/chromium/issues/detail?id=1124298 [3] https://fred-wang.github.io/MathFonts/mozilla_mathml_test/ Change-Id: I42ff3b821d2f2da201b1ff4a4612a8d5756486a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3081881 Commit-Queue: Frédéric Wang <[email protected]> Reviewed-by: Rob Buis <[email protected]> Cr-Commit-Position: refs/heads/master@{#910252}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.