FYI: Upstream Chromium window handling bug

The current www/chromium (chromium-152.0.7977.75_2) suffers from an upstream bug (which should be fixed in 153.0.8010.47). When launched from a desktop environment (button / menu), it does not switch into the correct scaling mode to react to window move/resize events.

The quick fix while waiting for this to filter down is to launch chrome from a terminal, or to disable "Use startup notification" in the launcher item.
 
Chrome is available on Windows (7+), macOS (10.15+), Linux (Ubuntu 18.04+, Debian 10+, Fedora 32+), Android (8.0+), iOS (15+), and ChromeOS. Release timing may vary slightly between platforms, with desktop typically releasing first.

None of the supported OS's use X, tho.....


In Chrome version 153, Chrome browser is moving to a 2-week release cycle. Read the announcement.

The Extended Stable channel provides a secure and stable option for enterprises that cannot accommodate a 2-week release cycle.

Release cycle and cadence​

To provide an Extended Stable release, Chrome browser maintains the milestone branch for 6 additional weeks by back-porting important security fixes to create an Extended Stable channel, where a new milestone is shipped every 8 weeks.

Given that Extended Stable is backporting fixes, where does that leave freebsd users that depend on the not so frequent successful pkg builds?
 
Back
Top