You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: Add a warning about updating the on attribute before upgrade (#809)
* fix Add a warning about updating the on attribute before upgrade
* fix Update documentation
* updating the changelog
* fix Move warning for on attribute into connectedCallback
* fix Remove on from storybook
* fix Remove references to on attribute from documentation and demos
* fix Add theme preview to stories for components that support theme
* fix Revert theming updates to storybook into a separate branch
Co-authored-by: Kendall Totten <[email protected]>
Co-authored-by: Kyle Buchanan <[email protected]>
Copy file name to clipboardExpand all lines: docs/content/develop/_index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Before getting started, it's important to note that because this is a library, e
25
25
- If it is a `container` component, then it should focus on creating sections in which components can be placed. These will handle surface colors, padding, some layout, but no typography styles. Examples include: `pfe-card`, `pfe-band`
26
26
- If it is a `combo` component, then it should not contain any styles of its own (exception: you might need to set the display value of the host) but rather, it will pull together other components into a set that is logical for content editors or developers. These components can also make decisions about the way the children components are laid out or which components are called based on built-in logic for that combo.
27
27
3. Components should be context aware, if possible.
28
-
-`Content` components should be equipped with styles for the `on="dark"` attribute, so that they can be used on both light and dark backgrounds.
28
+
-`Content` components should be equipped with styles for light, dark, and saturated backgrounds.
29
29
4. Framework agnostic
30
30
- A PatternFly Element should "just work" when you drop it onto any page (provided the proper polyfills are there). It should have ALL the styles it needs, when coupled with a PFE Theme.
31
31
@@ -44,7 +44,7 @@ A component always touches all four sides of its parent container. For example,
This component has attributes which invoke the multiple style changes on a call-to-action link. It also has `on="dark"`styles built-in so that colors will automatically adjust on dark surfaces
47
+
This component has attributes which invoke the multiple style changes on a call-to-action link. It has styles built-in so that colors will automatically adjust to surfaces.
Copy file name to clipboardExpand all lines: docs/content/theme/_index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ This is because the accent color should be the brightest and boldest, and the pr
28
28
Additionally, each component comes equipped to adjust its colors depending on where it's placed on the page. For example, should you need to put a default CTA (which is blue) on a dark blue card, the CTA will need to adapt. You can do this by informing the component of its context (on a dark background) by giving the `on` attribute the value of `dark`.
29
29
30
30
<pfe-card pfe-color="dark">
31
-
<pfe-cta pfe-color="base" on="dark">
31
+
<pfe-cta pfe-color="base">
32
32
<a href="#">Default</a>
33
33
</pfe-cta>
34
34
</pfe-card>
@@ -39,4 +39,4 @@ Should you need to deviate from this color usage, and set your primary CTA to us
39
39
<a href="#">Primary</a>
40
40
</pfe-cta>
41
41
42
-
Please note that if you are opting to override colors of components, they will not automatically respond to the `on="dark"` attribute any longer.
42
+
Please note that if you are opting to override colors of components, they will not automatically respond to the theme context any longer.
0 commit comments