-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Test/optional ignore style validation #39417
Conversation
Size Change: +5.39 kB (0%) Total Size: 1.16 MB
ℹ️ View Unchanged
|
Thanks for the PR @glendaviesnz I think the important thing to figure out right now is what do we really want to do with the "style" invalidation: 1- Do we want to allow block authors to consider changes to the style markup valid? Personally, I think if we do consider moving all "style" attributes to the server, it would create a lot of noise if we don't provide automatic migrations. Meaning, I think we should do one of these two approaches:
That said, I've been thinking that maybe we're putting the cart before the horse. Basically, maybe we should actually do the change (style engine v2 and move style to the server in an opt-in way) and then decide what to do with the invalidation when we switch the style server flag for a given block. |
Yes, and some of the work currently being done on validation by Dennis will also feed into these decisions, eg. #38794, #38923, #39523
I tend to agree. I think I will just close this PR for now - knowing how the move of styles is actually going to work via the style engine will help better inform exactly what is needed in terms of the validation handling. |
What?
Just a rough prototype to see if we can make ignoring styles in validation optional by block.
Related to #37942
Why?
How?
Testing Instructions
Screenshots or screencast