Skip to content
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

Submissions/opera microdata #24

Merged
merged 2 commits into from
Sep 23, 2013
Merged

Submissions/opera microdata #24

merged 2 commits into from
Sep 23, 2013

Conversation

darobin
Copy link
Contributor

@darobin darobin commented Feb 11, 2013

No description provided.

@Ms2ger
Copy link
Contributor

Ms2ger commented Feb 11, 2013

I need the manifest.

@jgraham jgraham closed this Feb 25, 2013
@jgraham jgraham reopened this Feb 25, 2013
@jgraham jgraham closed this Mar 9, 2013
@jgraham jgraham reopened this Mar 9, 2013
@zcorpan
Copy link
Member

zcorpan commented Sep 20, 2013

I think these have been reviewed when Mozilla implemented microdata. So, if the manifest is put back, I guess we can merge this.

jgraham added a commit that referenced this pull request Sep 23, 2013
@jgraham jgraham merged commit d620b80 into master Sep 23, 2013
@Ms2ger Ms2ger deleted the submissions/opera-microdata branch September 23, 2013 15:42
@Ms2ger
Copy link
Contributor

Ms2ger commented Sep 23, 2013

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 <fwang@igalia.com>
Reviewed-by: Rob Buis <rbuis@igalia.com>
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 <fwang@igalia.com>
Reviewed-by: Rob Buis <rbuis@igalia.com>
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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants