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

New principle: New features should not break existing ones #297

Open
atanassov opened this issue Mar 29, 2021 · 3 comments
Open

New principle: New features should not break existing ones #297

atanassov opened this issue Mar 29, 2021 · 3 comments
Assignees
@hober @atanassov
Labels
Status: Consensus to write We have TAG consensus about the principle but someone needs to write it (see "To Write" project)
Milestone
2021-08-02-week

Comments

@atanassov
Copy link
Contributor

This is a rather obvious principle and yet we don't have it at the moment. There are examples of features being proposed or worked on that have a direct negative affect to other features or user behavior. Unfortunately more often than not such affect goes to accessibility related features. It is worth spelling out this is undesirable.

A current example of such proposal is the content-visibility: auto and its effect to accessibility tree creation and consistency.
@atanassov atanassov self-assigned this Mar 29, 2021
@atanassov atanassov added the Status: Consensus to write We have TAG consensus about the principle but someone needs to write it (see "To Write" project) label Jun 7, 2021
@atanassov
Copy link
Contributor Author

Related to #174

@torgo
Copy link
Member

torgo commented Jun 7, 2021

As discussed today, we think this can be accomplished by bringing over some additional text from the HTML design principles. @hober will work on this. #174.

@torgo torgo added this to the 2021-06-07-week milestone Jun 7, 2021
@torgo torgo modified the milestones: 2021-06-07-week, 2021-08-02-week Aug 1, 2021
@cynthia cynthia mentioned this issue Dec 13, 2021
Merged
@hober hober changed the title New principle: New features must not break existing ones New principle: New features should not break existing ones Apr 21, 2023
@torgo
Copy link
Member

torgo commented Apr 21, 2023

We discussed at the Tokyo f2f and there is some stuff - in our minutes [to be published soon] - which @hober will turn into a principle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hober hober

@atanassov atanassov

Labels
Status: Consensus to write We have TAG consensus about the principle but someone needs to write it (see "To Write" project)
Projects
None yet
Milestone
2021-08-02-week
Development

No branches or pull requests
3 participants
@hober @torgo @atanassov