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.

Sign up for GitHub

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

Jump to bottom

Measure 'available' for region extent excludes padding and border. #351

Closed
nigelmegitt opened this issue May 31, 2017 · 0 comments
Closed

Measure 'available' for region extent excludes padding and border. #351

nigelmegitt opened this issue May 31, 2017 · 0 comments
Labels
pr merged substantive
Milestone
1ED-CR1

Comments

@nigelmegitt
Copy link
Contributor

See #348 (review) for background; this arose from review of the pull request to address #215.

When the auto keyword is used in tts:extent as part of a <measure> it resolves to available however the specification for available excludes border and padding, whereas for region elements we wish to include border and padding when we define the size.
@nigelmegitt nigelmegitt mentioned this issue May 31, 2017
Merged
@skynavga skynavga self-assigned this May 31, 2017
@skynavga skynavga added this to the Editor's WR Work List milestone May 31, 2017
@skynavga skynavga changed the title available measure for region extent excludes padding and border Measure 'available' for region extent excludes padding and border. May 31, 2017
@skynavga skynavga removed this from the Editor's WR Work List milestone May 31, 2017
skynavga added a commit that referenced this issue Jan 27, 2018
@skynavga
Map measure 'auto' on region to '100%' rather than 'available' (#351).
03a3934
@skynavga skynavga mentioned this issue Jan 27, 2018
Merged
@skynavga skynavga added this to the Editor's CR Work List milestone Jan 27, 2018
skynavga added a commit that referenced this issue Feb 9, 2018
@skynavga
Merge pull request #593 from w3c/issue-0351-region-available
dd0ec19 
Map measure 'auto' on region to '100%' rather than 'available' (#351).
@skynavga skynavga removed their assignment Feb 9, 2018
@skynavga skynavga added pr merged and removed pr open labels Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pr merged substantive
Projects
None yet
Milestone
1ED-CR1
Development

No branches or pull requests
3 participants
@skynavga @nigelmegitt @tmichel07