Bug 38090 - The UX for custom notice styling per notice template is confusing
Summary: The UX for custom notice styling per notice template is confusing
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Notices (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 35267
Blocks:
  Show dependency treegraph
 
Reported: 2024-10-04 07:34 UTC by Martin Renvoize (ashimema)
Modified: 2024-10-07 16:05 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Renvoize (ashimema) 2024-10-04 07:34:27 UTC
A couple of people have highlighted now that the adding of a 'Format' section amongst the message transport types in the notice template editor is confusing.

The feature itself is also a little misleading as people presumed from the title that it affected print-type notices only, when in fact it affects all notice types when printed.

The distinction is subtle, but makes a large difference in expectations.

I'm not sure how to proceed here, but I want it recorded as a bug to see if anyone can come up with a cleaner approach for end users.
Comment 1 Martin Renvoize (ashimema) 2024-10-07 14:03:01 UTC
I believe we should forget the 'print' part of the bug title in 33478.. in fact the feature actually just allows one to specify CSS per message template + transport type combination (though the UI also allows for explicitly copying said styling to all message transport types for the message template.

In reality, I think we should be encouraging the use of `@media print {}` to scope CSS to print only rules rather than trying to define this "in code"