Bug 1893568 Comment 7 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I'm inclined to agree.  I confirmed the regression range is just bug 1848715, running mozregression with `browser.urlbar.trimHttps` set to false.

mak: kind of a tight turnaround given that 127 goes to release next week, but given this regression, does it seem feasible to back it out (probably from Nightly and beta), given that it had unforeseen visual regression on release builds beyond the nightly-specific-for-now `browser.urlbar.trimHttps` configuration that it was meant to target?
Revision 1 by
on 
I'm inclined to agree.  I confirmed the regression range is just bug 1848715, running mozregression with `browser.urlbar.trimHttps` set to false.

mak: kind of a tight turnaround given that 127 goes to release next week, but given this regression, does it seem feasible to back it out (probably from Nightly and beta), given that it had unforeseen visual regression on release builds beyond the nightly-specific-for-now `browser.urlbar.trimHttps` configuration that I think bug 1848715 was meant to target?

Back to Bug 1893568 Comment 7