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

[css‑text‑4] Consider renaming text‑wrap: nowrap to text‑wrap: no‑wrap #5376

Open
ExE-Boss opened this issue Jul 31, 2020 · 6 comments

Comments

@ExE-Boss
Copy link
Contributor

See the first point of the List of Legacy Mistakes in the Design of CSS.

I don’t think we should repeat that mistake again.

@ExE-Boss ExE-Boss changed the title [css‑text] Rename text‑wrap: nowrap to text‑wrap: no‑wrap [css‑text‑4] Consider renaming text‑wrap: nowrap to text‑wrap: no‑wrap Jul 31, 2020
@Loirooriol
Copy link
Contributor

Too many sites rely on nowrap, it can't be changed. Adding no-wrap as an alias would be possible, but was already rejected in #1537. Do you have new arguments to reconsider that resolution?

@ExE-Boss
Copy link
Contributor Author

ExE-Boss commented Jul 31, 2020

This isn’t about white‑space, this is about the new CSS Text 4 text‑wrap property, which no engines are shipping yet.

@frivoal
Copy link
Collaborator

frivoal commented Aug 1, 2020

text-wrap is a longhand of white-space though, so nowrap is the same keyword with the same meaning. Shorthand/longhand relationships are flexible enough that we could map nowrap in one to no-wrap in the other, but that seems very confusing to me.

@ExE-Boss
Copy link
Contributor Author

ExE-Boss commented Aug 1, 2020

@frivoal Well, if #5382 is accepted, then it will make distinguishing the <white‑space‑legacy> nowrap value from the <'text‑wrap'> no‑wrap value much easier.

@fantasai
Copy link
Collaborator

I'm very certain that we are not going to rename nowrap to no-wrap, simply for consistency with white-space and flex-wrap. At most we would add an alias--for all instances of nowrap.

@tabatkins
Copy link
Member

Yes, we're currently consistently bad with nowrap, which sucks, but it's better than some properties having nowrap and others having no-wrap. Accepting both would be ideal.

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

5 participants