Gerrit commit message body is always wrapped with MS Edge 44.17763.1.0 and does not respect any line feeds.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | QChris | T186406 Polygerrit Outgoing reviews, Incoming reviews and Recently closed headings should be more different from commits | |||
| Resolved | None | T220801 PolyGerrit 2.15 UI does not support custom dashboards (supported from in 2.16+) | |||
| Resolved | QChris | T206453 Big empty space under patch description | |||
| Restricted Task | |||||
| Resolved | None | T210515 context links in diff don't use pointer cursor | |||
| Resolved | Paladox | T223278 "Server error: line 1:33 no viable alternative at character '['" when visiting particular patch | |||
| Restricted Task | |||||
| Resolved | hashar | T103990 Gerrit upload-pack send ALL references causing massive network I/O on common operations | |||
| Resolved | None | T195280 New Gerrit UI does not contain copyable Change-Id or parent commit id | |||
| Declined | Feature | None | T201246 Make a PolyGerrit plugin to welcome new users | ||
| Resolved | QChris | T254158 Gerrit 3.2 upgrade | |||
| Declined | None | T256964 Gerrit commit message body is always wrapped with MS Edge |
Event Timeline
Comment Actions
If I understood CSS properly, the wrapping rule comes from the first rule in:
:host([pre]) span { white-space: var(--linked-text-white-space, pre-wrap); word-wrap: var(--linked-text-word-wrap, break-word); }
And Microsoft Edge should support white-space: pre-wrap according to https://caniuse.com/#feat=mdn-css_properties_white-space_pre-wrap , and it supports var() as well. We would need to look at the dom/css rule applied to the element.
There are some demos at https://developer.mozilla.org/en-US/docs/Web/CSS/white-space :)
Comment Actions
This is unlikely to be ever solved, the recommendation is to use Chromium. Firefox works well as well in my experience, there are some time issues with it but upstream is happy to fix them when we report them.
For Microsoft Edge, it is based on Chromium, so I can imagine a more recent version of Edge would fix the issue encountered. Else you would have to switch to Chromium or Firefox.
Comment Actions
so I can imagine a more recent version of Edge would fix the issue
I’ve forgotten this task, sorry. I can confirm that a more recent Edge solved this issue.