Summary: | Notice display modal should respect 'email' message transport type | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize (ashimema) <martin.renvoize> |
Component: | Notices | Assignee: | Martin Renvoize (ashimema) <martin.renvoize> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | david, dcook |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | 39410 | ||
Bug Blocks: |
Description
Martin Renvoize (ashimema)
2025-04-15 14:41:16 UTC
Email clients typically support: * Inline CSS only * Basic tags (<table>, <tr>, <td>, <p>, <img>, <a>, etc.) * No <style>, <script>, or modern CSS like flexbox, grid, etc. Perhaps I'm looking at this from the wrong level.. we should be considering this when generating email type notices and use an inliner or transposer to convert our modern HTML template driven notices to the restricted rules from above. We could even bundle something like https://bootstrapemail.com/. This sounds pretty interesting. Some of the local feedback I got for bug 11583 was about generating previews but I didn't feel confident that we could do a really good preview. This could help a lot with that. We could even add some advice near the editor to tell people to keep it simple as you've described, Martin. I notice sometimes that libraries want to do these really elaborate emails, but simpler is better imho... |