blink::HTMLMediaElement::ShouldReusePlayer: avoid dereferencing a potentally NULL domWindow

The domWindow() method of the Document class can potentially return nullptr
as noted in renderer/core/dom/document.h

> // A document may or may not have a browsing context
> // (https://html.spec.whatwg.org/#browsing-context). A document with a browsing
> // context is created by navigation, and has a non-null domWindow(), GetFrame(),
> // Loader(), etc., and is visible to the user. It will have a valid
> // GetExecutionContext(), which will be equal to domWindow(). If the Document
> // constructor receives a DocumentInit created WithDocumentLoader(), it will
> // have a browsing context.
> // Documents created by all other APIs do not have a browsing context. These
> // Documents still have a valid GetExecutionContext() (i.e., the domWindow() of
> // the Document in which they were created), so they can still access
> // script, but return null for domWindow(), GetFrame() and Loader(). Generally,
> // they should not downcast the ExecutionContext to a LocalDOMWindow and access
> // the properties of the window directly.

Upon checking further, the offending document returns null for GetFrame() and
Loader() aswell so this was likely just an oversight and no invariants are being
violated

Introduced in https://chromium-review.googlesource.com/c/chromium/src/+/4202152

More details https://bugs.chromium.org/p/chromium/issues/detail?id=1447388

Fixed: 1447388
Change-Id: I85a6ef52baaac0ec7f5ec188d5d5bb2c518a8ecd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4546610
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/main@{#1147184}
2 files changed
tree: fb348858a40f834059f67929c085481231d87642
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. WATCHLISTS
README.md

Logo Chromium

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.