Code blocks unreadable with OWA email client in Conversations mode (#429223) · Issues · GitLab.org / GitLab

Code blocks unreadable with OWA email client in Conversations mode

<details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=429223) </details>  ### Summary As suggested in https://gitlab.com/gitlab-org/gitlab/-/issues/364820#note_1615148460, I'm opening new issue about similar problem. Currently, Outlook OWA renders incorrectly code blocks of any type in Conversations view. ### Steps to reproduce - Receive email with any code block (inline or not) which became Conversation - Code text size in unreadable tiny ### What is the current *bug* behavior? ![image](/uploads/f500dd07027411bc2e90871335ad0cc2/image.png) ```html inline code block 2 <font face="var(--default-mono-font,GitLab Mono,),JetBrains Mono,Menlo,DejaVu Sans Mono,Liberation Mono,Consolas,Ubuntu Mono,Courier New,andale mono,lucida console,monospace" size="2" color="#333238" style="font-family: monospace, serif, EmojiFont;">code block 2 ``` ### What is the expected *correct* behavior? ![image](/uploads/58bce8e2cc39300fa47a878b4909cd9f/image.png) ```html <code style="font-size:0.875rem; color:#1f1e24; word-wrap:break-word; background-color:#ececef; border-radius:4px; margin-top:0; font-weight:inherit; white-space:pre-wrap; word-break:keep-all; padding:2px 4px">inline code block</code> <code style="font-size:0.875rem; color:inherit; word-wrap:normal; word-break:keep-all; background-color:inherit; border-radius:4px; white-space:pre; margin-top:0; padding:unset">code block</code> ``` ### Relevant logs and/or screenshots As you can see above - `html` for messages completely different. Both messages are the same (except `2`), but when they became conversation - format became broken. ![image](/uploads/1ab80742d1b3dbf156956190a012ea49/image.png) #### Results of GitLab environment info <details> <summary>Expand for output related to GitLab environment info</summary> <pre> [root@gitlab ~]# gitlab-rake gitlab:env:info System information System: Current User: git Using RVM: no Ruby Version: 3.0.6p216 Gem Version: 3.4.19 Bundler Version:2.4.20 Rake Version: 13.0.6 Redis Version: 7.0.13 Sidekiq Version:6.5.7 Go Version: unknown GitLab information Version: 16.5.0 Revision: c4532d87456 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 13.11 URL: https://gitlab.. HTTP Clone URL: https://gitlab../some-group/some-project.git SSH Clone URL: git@gitlab..:some-group/some-project.git Using LDAP: yes Using Omniauth: yes Omniauth Providers: GitLab Shell Version: 14.29.0 Repository storages: - default: unix:/var/opt/gitlab/gitaly/gitaly.socket GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Gitaly - default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket - default Version: 16.5.0 - default Git Version: 2.42.0 </pre> </details> #### Results of GitLab application Check <details> <summary>Expand for output related to the GitLab application check</summary> <pre> [root@gitlab ~]# gitlab-rake gitlab:check SANITIZE=true Checking GitLab subtasks ... Checking GitLab Shell ... GitLab Shell: ... GitLab Shell version >= 14.29.0 ? ... OK (14.29.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... yes Number of Sidekiq processes (cluster/worker) ... 1/1 Checking Sidekiq ... Finished Checking Incoming Email ... Incoming Email: ... Reply by email is disabled in config/gitlab.yml Checking Incoming Email ... Finished Checking LDAP ... LDAP: ... Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) User output sanitized. Found 100 users of 100 limit. Checking LDAP ... Finished Checking GitLab App ... Database config exists? ... yes Tables are truncated? ... skipped All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Cable config exists? ... yes Resque config exists? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units) Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units) Projects have namespace: ... ... 425/432 ... yes Redis version >= 6.0.0? ... yes Ruby version >= 3.0.6 ? ... yes (3.0.6) Git user has default SSH configuration? ... yes Active users: ... 103 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Checking GitLab App ... Finished Checking GitLab subtasks ... Finished </pre> </details>

issue