The Library button has different old styling. This is just because the default button styling is not in scope. I'm not sure it is worth importing all those button styling rules.
The icon is center aligned with the message box, rather than aligned with the bold title. The mozilla message-bar element doesn't have an easy way to control this because the icon lives in a shadow root, so doesn't share the styling rules with the rest of the content.
In the first case, I think we can probably leave this until mozilla imports the common.css styling into places.xhtml, or just re-implements that since it is pretty old. The (possibly-inactive) bugzilla 1788947 may be relevant.
In the latter case, it is do-able by us if we modify the <message-bar> widget code, but mozilla might also be interested in doing this if they want to start using the widget in a similar way. E.g. in about:preferences there are some multi-line message boxes where they might want to eventually use this.
Designs
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
I'll see if moz-message-bar entirely resolves this issue, otherwise I'll split the transition from message-bar to moz-message-bar into a separate issue.
@donuts I've had a look at moz-message-bar and it is not a direct replacement for the message-bar element we currently use.
Here are a few screenshots that show what a quick conversion to moz-message-bar looks like.
In about:downloads:
In the "Library" window (bookmarks window Ctlr+Shift+O):
In the downloads panel:
First thing to note is that it doesn't fix the button styling in the "Library" window, but it does address the icon alignment for us.
A few questions:
Do we want to switch to moz-message-bar or manage our own component?
Do we want to also switch the downloads panel to use this style? Currently it is styled using its own rules, but we could use moz-message-bar here as well. It would be easier to maintain if all three locations for the message use the same layout.
Do we want to add a full-stop to the end of "Be careful opening downloads"? I think it might help with readability when the body text is on the same line. It may have an effect on screen readers (would have to check).
We would have to modify moz-message-bar to keep the "Tails" string as a link to the Tails website. It is do-able, but it would require a small amount of maintenance with each ESR since it is mozilla code. Is it worth it?
Do we want a warning icon instead of the "info" icon?
Do we want to switch to moz-message-bar or manage our own component?
Let's use the moz component for ease of maintainability, please.
Do we want to also switch the downloads panel to use this style? Currently it is styled using its own rules, but we could use moz-message-bar here as well. It would be easier to maintain if all three locations for the message use the same layout.
Yes, that makes sense to me too.
Do we want to add a full-stop to the end of "Be careful opening downloads"? I think it might help with readability when the body text is on the same line. It may have an effect on screen readers (would have to check).
We would have to modify moz-message-bar to keep the "Tails" string as a link to the Tails website. It is do-able, but it would require a small amount of maintenance with each ESR since it is mozilla code. Is it worth it?
Is there a "Support link" we could hijack for this purpose instead (see design docs above), with a call to action to learn more about Tails?
Do we want a warning icon instead of the "info" icon?
I'm in two minds as to whether or not this should be considered informational vs a warning, however if we were to go with a warning icon, I think the whole message bar should change to the warning type (i.e. become yellow).
Any other tweaks to make?
Yes please – could you remove the upper of the two horizontal rules in the downloads panel please? It's no longer necessary now that the warning itself includes its own perimeter.
@donuts thanks for the feedback, I'll start putting something together then.
Is there a "Support link" we could hijack for this purpose instead (see design docs above), with a call to action to learn more about Tails?
I couldn't find a support page that explains both proxy-leaks via downloaded files, and Tails as a solution, so I don't think we could use a simple "Learn more" that wouldn't be confusing. Maybe it would be worth creating such a page in "about:manual".
Otherwise, I guess we could do
To be safe, open files while offline or use a portable operating system like Tails. Learn more about Tails
I couldn't find a support page that explains both proxy-leaks via downloaded files, and Tails as a solution, so I don't think we could use a simple "Learn more" that wouldn't be confusing. Maybe it would be worth creating such a page in "about:manual".
This appears to be another case of there being relevant content on the support portal that isn't present on the manual: