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
I'm using component to display feedback on action like this:
As you can see, I'm using a unordered list to display errors (in that case). I have several cases like this where I want to provide feedback via an Alert component as separate items. That's not how the DSFR Alert component has been designed, as its description should simply be included in <p> tag (as per documentation : https://www.systeme-de-design.gouv.fr/elements-d-interface/composants/alerte/).
The issue is that including <ul> in a <p> is not valid HTML (and produces warning in the console...).
Should we stick to the DSFR markup? Switch to a generic <div> instead of a <p> ? Maybe the DSFR team is ok with using an other tag than the <p>?
The text was updated successfully, but these errors were encountered:
I did ask the DSFR team about this (https://mattermost.incubateur.net/betagouv/pl/pjiwmqbc8bb7znk86aqh49h8xc). It seems that the example in the doc is just a markup example, that can be adjusted (e.g. using an <ul> to show errors as list). I'll push something to adjust our component to handle it in a few days.
I'm using component to display feedback on action like this:
As you can see, I'm using a unordered list to display errors (in that case). I have several cases like this where I want to provide feedback via an Alert component as separate items. That's not how the DSFR Alert component has been designed, as its description should simply be included in
<p>
tag (as per documentation : https://www.systeme-de-design.gouv.fr/elements-d-interface/composants/alerte/).The issue is that including
<ul>
in a<p>
is not valid HTML (and produces warning in the console...).Should we stick to the DSFR markup? Switch to a generic
<div>
instead of a<p>
? Maybe the DSFR team is ok with using an other tag than the<p>
?The text was updated successfully, but these errors were encountered: