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

Clarify our Mission Statement and Process #21

Closed
bramus opened this issue Aug 26, 2022 · 3 comments
Closed

Clarify our Mission Statement and Process #21

bramus opened this issue Aug 26, 2022 · 3 comments

Comments

@bramus
Copy link
Collaborator

bramus commented Aug 26, 2022

In this repository’s README there is short goal – or “Mission Statement” if you would like to call it that way – which was quoted from here:

To sort out any confusion about what “viewport” means, and what browsers (especially on mobile devices) should be doing with various viewport measurements & sizing. To make recommendations for what should change to improve interoperability.

It has come to my attention that this is not clear, given the pushback in the following issues:

To be clear: yes, the plan is to pursue clarification/resolution/… at the proper venues that have the authority to do so (e.g. CSSWG), file bugs with the relevant vendors, etc.

Note that this was mentioned during previous meetings #3 and #4, but not reflected in the notes. Apologies for failing to properly write up meeting notes, making this unclear to external people / people who were not able to attend.

As also mentioned during the previous meetings I am very open to feedback on the current process, and would like to discuss this first during the next meeting.

/cc @jensimmons @karlcow @fantasai

@karlcow
Copy link

karlcow commented Aug 29, 2022

There are two sentences in the scope of the work which I think represent the intent of what @jensimmons had written in the passage you quoted which is in the goal.

Open any issues at CSSWG, WHATWG, wherever if we find underspecified standards on what these measurements should be in relationship to the viewport — so that the appropriate standards group can take it from there & define any missing details.
Open any issues/bugs with the appropriate browsers, noting places where they are not aligned with the standard. Or if the standard is unclear, where they are not aligned with each other.

@foolip
Copy link
Member

foolip commented Aug 29, 2022

I think it would be great to put some of that language into the README to document how we will work.

The linked issues would make sense to file as spec issues, and I don't think there's any disagreement about that, just a question of when it happens. Soonish, I presume.

@bramus
Copy link
Collaborator Author

bramus commented Sep 7, 2022

Discussed during #20. We will include the extra wording to make our intentions clear.

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

3 participants