chromium's clipping bounds assumed vertical tabs were always on the
left, causing side panel contents to be clipped when tabs were
right-aligned.
fixes#2247
the selectable-area check still assumed the alert indicator was on the
trailing edge. measure the title area after the indicator instead so
mute toggling remains enabled on sufficiently wide inactive tabs.
hopefully fixes#2058
- native-frame-materials: move the hover guard back to
IsApparentlyActive(). the refresh accidentally moved it to GetZValue()
- infobar/vertical: bring back the separator above infobars, clipped to
content area like in m150. reuse the regular contents separator below.
drop hunks that were previously removed by zen patch.
- inox-patchset: add missing paint_preview buildflags dep to
external_protocol, the generated header could race on clean builds
- drop no-op avatar branch, unused includes, and whitespace-only hunks
added by merge commit
the updated dependencies include updated icons, search engine
descriptions, and addition of startpage and brave search.
we now also use nonfree assets builds from a proper source of truth
(imputnet/helium-nonfree-assets) instead of a random gist.
this PR:
- adds startpage and brave search, and fixes its names
- removes related favicon and logo urls to prevent unintentional
requests
- bumps prepopulated_engine's `kCurrentDataVersion` to make sure
existing profiles get new engines ahead of upstream bump
closes#92closes#177closes#618
now users can toggle helium noise globally or per origin/domain
(including wildcards). this change also gives fingerprinting protection
a home with a description of how it works.
- added a global pref for helium noise
- added origin-based content setting for helium noise
- added a settings helper for getting the noise activation state
- added a page and an entry point to browser privacy settings
- added page info controls for helium noise for quick per-origin changes
- cleaned up noise includes and public header registration
AppKit can re-enter hit testing while `BrowserWidget` is being
destroyed. At that point `browser_widget_` has already been cleared, but
`BrowserView` may still be attached, so `GetWidget()` remains non-null.
Also check `browser_widget_` to avoid dereferencing it during teardown.
fixes#2129
use weak pointers async callbacks instead of base::Unretained(this), and
move BangManager's weakptrfactory to the end of the class so callbacks
are invalidated before other members are destroyed
fixes#1030
jj