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
Since we updated a few mime icons (doc, spreadsheets, pdf, archives...), we stepped away from the themed mime icons to use either org-provided colors (like red for pdf, blue for docx...) or fallback to the standard grey #969696
I am not sure we benefit from supporting the svg coloring feature the mime API provides.
As of technical debt, I think we could deprecate and remove it.
cc @nextcloud/designers @nextcloud/server-frontend
Goal
The goal is to agree on a line to follow from here. If the design team is ok with this:
if the mime is associated with a specific color, often provided by the org that created this file type, use it
else, fallback to a default #969696 grey
if folder, we always use the primary color
The text was updated successfully, but these errors were encountered:
I agree here, but additionally I would suggest to move to an inline-svg approach. Because currently it is not really possible to get the correct primary color.
The color depends on:
Theme the user uses
Preferred color schema of the browser
The first is "easy" to get on the backend, the second only with some new browser stuff not supported by e.g. Firefox.
So instead if we move to inline svgs instead of background images, we could simply use fill: var(--color-primary-element).
The proposal sounds good from the design side. It helps folders, files with previews and specific file types (PDF, docs, spreadsheets, slides) to stand out.
Since we updated a few mime icons (doc, spreadsheets, pdf, archives...), we stepped away from the themed mime icons to use either org-provided colors (like red for pdf, blue for docx...) or fallback to the standard grey
#969696
I am not sure we benefit from supporting the svg coloring feature the mime API provides.
As of technical debt, I think we could deprecate and remove it.
cc @nextcloud/designers @nextcloud/server-frontend
Goal
The goal is to agree on a line to follow from here. If the design team is ok with this:
#969696
greyThe text was updated successfully, but these errors were encountered: