-
Notifications
You must be signed in to change notification settings - Fork 30
Additional attributes for targeting meta elements #14407
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
Conversation
1886fa9
to
ec4aba5
Compare
Hello 👋! When you're ready to run Chromatic, please apply the You will need to reapply the label each time you want to run Chromatic. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like these sensible additions. Will be interesting to see if/how our Interactives colleagues make use of this new signage.
@@ -62,7 +66,7 @@ export const Dateline = ({ | |||
); | |||
} | |||
return ( | |||
<div css={datelineStyles} style={mobileColour}> | |||
<div css={datelineStyles} style={mobileColour} data-gu-name="dateline"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just looking out of curiosity so feel free to ignore. Do we ever have to care about primary vs. secondary datelines? Whatever that means 😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was chatting with the Ed Design crew about this earlier and apparently the distinction comes when a piece has been updated. In those cases you have publication date and and last modified date. So I think both pop up.
Seen on PROD (merged by @frederickobrien 7 minutes and 58 seconds ago) Please check your changes! |
Following chats with the Editorial Design crew this introduces several new
gu-data
attributes so that interactive atoms can target elements more consistently across web and apps.There's a possibly a larger piece of work to pick up here around keeping web/apps DCAR as tightly aligned as possible, as well as a discussion to be had about formalising the atom contract. What elements/data attributes can we count on always being there?
Still, one thing at a time. Getting this out will allow us to test the waters and make adjustments accordingly.