-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Block Validation: Ignore markup changes for the style attribute. #37851
Copy link
Copy link
Closed
Labels
Needs DevReady for, and needs developer effortsReady for, and needs developer efforts[Feature] Block Validation/DeprecationHandling block validation to determine accuracy and deprecationHandling block validation to determine accuracy and deprecation[Feature] ParsingRelated to efforts to improving the parsing of a string of data and converting it into a different fRelated to efforts to improving the parsing of a string of data and converting it into a different f[Type] EnhancementA suggestion for improvement.A suggestion for improvement.
Metadata
Metadata
Assignees
Labels
Needs DevReady for, and needs developer effortsReady for, and needs developer efforts[Feature] Block Validation/DeprecationHandling block validation to determine accuracy and deprecationHandling block validation to determine accuracy and deprecation[Feature] ParsingRelated to efforts to improving the parsing of a string of data and converting it into a different fRelated to efforts to improving the parsing of a string of data and converting it into a different f[Type] EnhancementA suggestion for improvement.A suggestion for improvement.
Type
Fields
Give feedbackNo fields configured for issues without a type.
In #37495 we're discussing how to bring more coherence and consistency to the styles resulting from block customizations.
One of the "conclusions" of that discussion is that we should probably not consider a block that have differences in the wrapper level style attribute as invalid block.
So basically if the markup of the block is
and the expected result is
The block should still be considered valid.
I'm creating this issue so we can track that and start exploring that change to the validation algorithm.
cc @andrewserong @aaronrobertshaw @mcsf @mtias
Related #21703