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

Merge css/css-block into css-display #7652

Closed
foolip opened this issue Oct 10, 2017 · 0 comments
Closed

Merge css/css-block into css-display #7652

foolip opened this issue Oct 10, 2017 · 0 comments

Comments

@foolip
Copy link
Member

foolip commented Oct 10, 2017

These tests were for https://drafts.csswg.org/css-box-3/, which isn't actively maintained.

@tabatkins says that "these can be moved to Display, mostly".

@foolip foolip changed the title Merge css/css-block-3 into css-display-3 Merge css/css-block into css-display Nov 9, 2017
foolip added a commit that referenced this issue Nov 24, 2017
Because `display: run-in` is not widely implemented, having these
tests in a directory of their own is very handy, so that they can be
skipped as a group. It also has its own spec section:
https://drafts.csswg.org/css-display/#run-in-layout

Only one test used a support file, and that support file wasn't used
by any other test at the origin directory.

Part of #7652.
foolip added a commit that referenced this issue Nov 25, 2017
All of these tests have 'run-in' in the filename or test title,
with the lone exception first-line-pseudo-009.xht which isn't primarily
testing `display: run-in` but still depends on it.

The only changes are to some relative paths. (Using absolute paths here
would be shorter and more robust when renaming, but it isn't done
anywhere else in /css/, so be consistent.)

Fixes #7652.
foolip added a commit that referenced this issue Nov 27, 2017
All of these tests have 'run-in' in the filename or test title,
with the lone exception first-line-pseudo-009.xht which isn't primarily
testing `display: run-in` but still depends on it.

The only changes are to some relative paths. (Using absolute paths here
would be shorter and more robust when renaming, but it isn't done
anywhere else in /css/, so be consistent.)

Fixes #7652.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant