commit | 0b55de11cd80c1210869466067343eba3181c795 | [log] [tgz] |
---|---|---|
author | Wojciech Zwonarz <wzwonarz@google.com> | Mon May 12 19:29:44 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 12 19:29:44 2025 |
tree | 097a6355412e02d740de919790890ea807b0f10a | |
parent | 9ed00118319c25081478226776fe9968e144f84a [diff] |
[M137] Fix for crash in FullscreenHtmlApiHandlerBase when no active tab Original change's description: > Fix for crash in FullscreenHtmlApiHandlerBase when no active tab > > When no active tab is set in the FullscreenHtmlApiHandlerBase the Null > Pointer Exception is thrown when onMultiWindowModeChanged is called. The > issue is present when the window is exiting the fullscreen mode and no > active tab is set. > > Null pointer validation was added to the MultiWindowModeObserver > implementation. > > Bug: 414919914 > Bug: 410789979 > Change-Id: I65fa4349b548a98c87ece70355d1088a88adfb83 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6508871 > Reviewed-by: Sirisha Kavuluru <skavuluru@google.com> > Reviewed-by: Peter Conn <peconn@chromium.org> > Commit-Queue: Wojciech Zwonarz <wzwonarz@google.com> > Cr-Commit-Position: refs/heads/main@{#1456149} Bug: 416179315,414919914,410789979 Change-Id: I65fa4349b548a98c87ece70355d1088a88adfb83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6533234 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Chrome Cherry Picker <chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/7151@{#840} Cr-Branched-From: 8e0d32ed6e49a2415b16e5ed402957cac2349ce2-refs/heads/main@{#1453031}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.