-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Forbid deprecated break-word
in CSS
#30934
Conversation
Also see tailwindlabs/tailwindcss#12127 and specifically https://play.tailwindcss.com/o2CjmfmOzJ which makes a point for |
Yeah but they set these, which imho make it a unrealistic example:
I think https://play.tailwindcss.com/o2CjmfmOzJ is more realistic, only that we don't set |
Here is that example with flex, shows exact same wrapping as grid: |
* giteaofficial/main: [skip ci] Updated licenses and gitignores Fix file path width in repo non-homepage view (go-gitea#30951) Enable `declaration-block-no-redundant-longhand-properties` (go-gitea#30950) [skip ci] Updated translations via Crowdin Move reverproxyauth before session so the header will not be ignored even if user has login (go-gitea#27821) Use CSS `inset` shorthand (go-gitea#30939) Remove If Exist check on migration for mssql because that syntax required SQL server 2016 (go-gitea#30894) Update JS dependencies, add new eslint rules (go-gitea#30840) Fix some UI regressions for commit list (go-gitea#30920) Forbid deprecated `break-word` in CSS (go-gitea#30934) Check if reverse proxy is correctly configured (go-gitea#30890) Remove deprecated stuff for runners (go-gitea#30930)
Forbid deprecated
break-word
and fix all occurences.Regarding
overflow-wrap: break-word
vsoverflow-wrap: anywhere
:Example of difference: https://jsfiddle.net/silverwind/1va6972r/
Here it says:
I don't think this difference will make any practical impact as we are not hitting this rare scenario.