forked from chromium/chromium
-
-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there a way to use Netflix and other streaming services? #34
Labels
documentation
Improvements or additions to documentation
Comments
Doesn't this method of installing dummy libraries work anymore? |
Indeed, that method still works in 10.9. I also have a project here which will set it up automatically. (Sorry, I feel like I'm posting this everywhere today, but it's relevant!) |
@aeiouaeiouaeiouaeiouaeiouaeiou @Wowfunhappy I'll add some notice of DRM to README.md. |
Updated README.md. |
blueboxd
pushed a commit
that referenced
this issue
Nov 26, 2021
This CL is a follow-up of crrev.com/c/3206436 ("Add a header indicating the version of the WebTransport draft used") Since the header is not a pseudo header and no another way for extension authors to know the header, we should send it. (cherry picked from commit 3e0aba3) Bug: 1240935 Change-Id: I32161553b9c79375b3c43a9952fa48e1d4efcd35 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3210527 Commit-Queue: Yoichi Osato <yoichio@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Karan Bhatia <karandeepb@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#929515} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3216705 Reviewed-by: Yoichi Osato <yoichio@chromium.org> Reviewed-by: Devlin <rdevlin.cronin@chromium.org> Auto-Submit: Yoichi Osato <yoichio@chromium.org> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Jeevan Shikaram <jshikaram@chromium.org> Cr-Commit-Position: refs/branch-heads/4664@{#34} Cr-Branched-From: 24dc4ee-refs/heads/main@{#929512}
blueboxd
pushed a commit
that referenced
this issue
Jan 15, 2022
This reverts commit 6ff1599. Reason for revert: Seems to have caused browser_test failures on linux-chromeos-chrome https://ci.chromium.org/p/chrome/builders/ci/linux-chromeos-chrome/19698 rowserTestBase received signal: Segmentation fault. Backtrace: #0 0x563ae696f899 base::debug::CollectStackTrace() #1 0x563ae68d6683 base::debug::StackTrace::StackTrace() #2 0x563ae6ff8293 content::(anonymous namespace)::DumpStackTraceSignalHandler() #3 0x7f9ac9026040 (/lib/x86_64-linux-gnu/libc-2.27.so+0x3f03f) #4 0x563ae7720266 PrefChangeRegistrar::RemoveAll() #5 0x563ae7720222 PrefChangeRegistrar::~PrefChangeRegistrar() #6 0x563ae2f37095 std::__1::unique_ptr<>::reset() #7 0x563ae3696a1b policy::ActiveDirectoryMigrationManager::~ActiveDirectoryMigrationManager() #8 0x563ae3696a38 policy::ActiveDirectoryMigrationManager::~ActiveDirectoryMigrationManager() #9 0x563ae369a699 policy::BrowserPolicyConnectorAsh::~BrowserPolicyConnectorAsh() #10 0x563ae369a6fe policy::BrowserPolicyConnectorAsh::~BrowserPolicyConnectorAsh() #11 0x563ae6a0edbd BrowserProcessImpl::~BrowserProcessImpl() #12 0x563ae6a0edea BrowserProcessImpl::~BrowserProcessImpl() #13 0x563ae6a668e9 browser_shutdown::ShutdownPostThreadsStop() #14 0x563ae6a0e226 ChromeBrowserMainParts::PostDestroyThreads() #15 0x563ae349ef9b ash::ChromeBrowserMainPartsAsh::PostDestroyThreads() #16 0x563ae495d2d9 content::BrowserMainLoop::ShutdownThreadsAndCleanUp() #17 0x563ae495e53c content::BrowserMainRunnerImpl::Shutdown() #18 0x563ae495a9ce content::BrowserMain() #19 0x563ae555e819 content::RunBrowserProcessMain() #20 0x563ae555f8e0 content::ContentMainRunnerImpl::RunBrowser() #21 0x563ae555f431 content::ContentMainRunnerImpl::Run() #22 0x563ae555d209 content::RunContentProcess() #23 0x563ae555d861 content::ContentMain() #24 0x563ae6ff6f2b content::BrowserTestBase::SetUp() #25 0x563ae68bf947 InProcessBrowserTest::SetUp() #26 0x563ae3b0fbed testing::Test::Run() #27 0x563ae3b10520 testing::TestInfo::Run() #28 0x563ae3b10ce1 testing::TestSuite::Run() #29 0x563ae3b1a61a testing::internal::UnitTestImpl::RunAllTests() #30 0x563ae3b1a219 testing::UnitTest::Run() #31 0x563ae69d5af8 base::TestSuite::Run() #32 0x563ae688bfa1 BrowserTestSuiteRunnerChromeOS::RunTestSuite() #33 0x563ae70407b7 content::LaunchTests() #34 0x563ae688e77a LaunchChromeTests() #35 0x563ae688bf23 main chromium#36 0x7f9ac9008bf7 __libc_start_main #37 0x563ae134462a _start Original change's description: > Remote powerwash on Chromad via policy > > Implement remote powerwash on Chromad, using the recently added > ChromadToCloudMigrationEnabled policy. The powerwash will be used to > start the migration of AD managed devices into cloud management. Besides > having the new policy enabled, the device needs to be on the login > screen and the enrollment ID must have already been uploaded to > DMServer. > > Bug: 1209246 > Change-Id: I6a67b8a8a43c28bc5f03f27e96d0415f69b6bc83 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3141873 > Reviewed-by: Maksim Ivanov <emaxx@chromium.org> > Reviewed-by: Roman Sorokin <rsorokin@chromium.org> > Reviewed-by: Colin Blundell <blundell@chromium.org> > Commit-Queue: Felipe Andrade <fsandrade@chromium.org> > Cr-Commit-Position: refs/heads/main@{#959123} Bug: 1209246 Change-Id: If067abcf2a9289ebacaeb240b1f67749c305509c No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3389555 Auto-Submit: Scott Violet <sky@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#959243}
blueboxd
pushed a commit
that referenced
this issue
Feb 3, 2022
As we still didn't switch to use the new experimental backend for WinRT API on Windows, this patch extends the expiry date to keep providing the flag for users who prefer the new backend. Still the legacy WinMM based backend and new WinRT based backend have different pros and cons respectively. (cherry picked from commit a5fa6f2) Bug: 1278257 Change-Id: Ieb8161a6509337ba46b28867a5be5b10db2bbef1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3325720 Auto-Submit: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#950510} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3336924 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/4758@{#34} Cr-Branched-From: 4a2cf4b-refs/heads/main@{#950365}
blueboxd
pushed a commit
that referenced
this issue
Jun 22, 2022
The bug here is that SwiftUI Images initialized via a UIImage don't properly adjust in dark mode. To solve this, they are initialized from the image name instead. Some are still initiialized via UIImage, but those are all template images, which adjust fine. (cherry picked from commit 6a9dc77) Bug: 1324516 Change-Id: Ia5d8e0f6021511d2ad377f6f2ff34f19c6f275f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3647725 Auto-Submit: Robbie Gibson <rkgibson@google.com> Reviewed-by: David Jean <djean@chromium.org> Commit-Queue: David Jean <djean@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1003316} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3650882 Commit-Queue: Robbie Gibson <rkgibson@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5060@{#34} Cr-Branched-From: b83393d-refs/heads/main@{#1002911}
blueboxd
pushed a commit
that referenced
this issue
Aug 31, 2022
How: Use the previous url in the redirect chain when computing the reporting origin for a redirect navigation The current approach contains an error, as at the time of DidRedirectNavigation() the NavigationHandle already reflects the URL which was redirect to (rather than redirected from). (cherry picked from commit 88a7440) Bug: 1347096 Change-Id: I2574502b22995fb63416bc7f281489e308f09287 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3779844 Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org> Reviewed-by: Nan Lin <linnan@chromium.org> Commit-Queue: John Delaney <johnidel@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1028025} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3787626 Owners-Override: Ben Mason <benmason@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Reviewed-by: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/branch-heads/5195@{#34} Cr-Branched-From: 7aa3f07-refs/heads/main@{#1027018}
blueboxd
pushed a commit
that referenced
this issue
Sep 29, 2022
This reverts commit aaaa0e3. Reason for revert: crbug.com/1354945 Original change's description: > [Dr-Dc] Add more devices to be blocklisted. > > Add more devices to be blocklisted here in chrome code since adding it > via finch is very slow. > > (cherry picked from commit 50a85fa) > > Bug: 1340054 > Change-Id: I3343d67ede012765fbfe36d6feb34a505d1a389e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3842363 > Auto-Submit: vikas soni <vikassoni@chromium.org> > Commit-Queue: vikas soni <vikassoni@chromium.org> > Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org> > Cr-Original-Commit-Position: refs/heads/main@{#1037178} > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3840823 > Reviewed-by: vikas soni <vikassoni@chromium.org> > Cr-Commit-Position: refs/branch-heads/5249@{#4} > Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826} Bug: 1340054 Change-Id: I20133a4a07dd9d389172a53585e39765cfbf8e4b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3848921 Owners-Override: Krishna Govind <govind@chromium.org> Commit-Queue: vikas soni <vikassoni@chromium.org> Reviewed-by: Krishna Govind <govind@chromium.org> Cr-Commit-Position: refs/branch-heads/5249@{#34} Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826}
blueboxd
pushed a commit
that referenced
this issue
Nov 30, 2022
(cherry picked from commit 989872e) Bug: 1366918 Change-Id: Ib516dba07df4deab377d01e1feb68a1cfc3d8505 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3943011 Reviewed-by: Chris Fredrickson <cfredric@chromium.org> Commit-Queue: Kirubel Aklilu <kaklilu@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1059263} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3960793 Auto-Submit: Kirubel Aklilu <kaklilu@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Chris Fredrickson <cfredric@chromium.org> Cr-Commit-Position: refs/branch-heads/5359@{#34} Cr-Branched-From: 27d3765-refs/heads/main@{#1058933}
blueboxd
pushed a commit
that referenced
this issue
Feb 8, 2023
Add metrics for feed card menu sign-in promo. (cherry picked from commit 3f658e3) Bug: 1401487 Change-Id: I9afc484ebb09b63effa8607a6b1fc0a633b9c981 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4104251 Reviewed-by: Justin DeWitt <dewittj@chromium.org> Commit-Queue: Tina Wang <tinazwang@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1084142} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4117572 Auto-Submit: Tina Wang <tinazwang@chromium.org> Commit-Queue: Justin DeWitt <dewittj@chromium.org> Reviewed-by: Adam Arcaro <adamta@google.com> Cr-Commit-Position: refs/branch-heads/5481@{#34} Cr-Branched-From: 130f3e4-refs/heads/main@{#1084008}
blueboxd
pushed a commit
that referenced
this issue
Mar 7, 2023
Change-Id: I2fb6404c3a7604529ad85bb7c70dc35f27f02a54 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4206307 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5563@{#34} Cr-Branched-From: 3ac59a6-refs/heads/main@{#1097615}
blueboxd
pushed a commit
that referenced
this issue
Apr 14, 2023
…oads This changes the partial view to open only when all downloads whose state was DownloadItem::IN_PROGRESS* have completed**, and not when initiating a download. The animated icon is still shown on initiating a download. To explain caveats: * We exclude any IN_PROGRESS downloads that are dangerous, except for those which are dangerous and pending deep scanning. Downloads pending deep scanning are considered in-progress because we want the user to interact with them by initiating deep scanning. ** Completed means reached a quiescent state, either paused or pending deep scanning, or excluded for being dangerous, or actually completed (i.e. no longer IN_PROGRESS). In fullscreen mode, if the partial view would have been shown normally, instead it is shown when the user exits fullscreen mode. This also fixes a bug whereby the animation was shown in all browser windows, not just the currently active window. (cherry picked from commit 4937aa6) Bug: 1416926 Change-Id: I4a7939180658ebebe96b25cf6026574995ca1974 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4284377 Reviewed-by: Xinghui Lu <xinghuilu@chromium.org> Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org> Commit-Queue: Lily Chen <chlily@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1109316} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4295919 Auto-Submit: Lily Chen <chlily@chromium.org> Commit-Queue: Xinghui Lu <xinghuilu@chromium.org> Cr-Commit-Position: refs/branch-heads/5615@{#34} Cr-Branched-From: 9c6408e-refs/heads/main@{#1109224}
blueboxd
pushed a commit
that referenced
this issue
May 9, 2023
(cherry picked from commit 9aafe90) Bug: 1427594 Change-Id: Iba6b14e710ef80350f9d2b7ef4cf813142e58cf5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4368207 Reviewed-by: Tommy Li <tommycli@chromium.org> Commit-Queue: Sophie Chang <sophiechang@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1122025} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4373882 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Sophie Chang <sophiechang@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5672@{#34} Cr-Branched-From: 5f2a724-refs/heads/main@{#1121455}
blueboxd
pushed a commit
that referenced
this issue
May 27, 2023
(cherry picked from commit 141a8e4) Fixed: 1439278 Change-Id: Icea34534172941c31336ca951d7da27ea88cee9b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4476653 Reviewed-by: Gauthier Ambard <gambard@chromium.org> Reviewed-by: Ewann Pellé <ewannpv@chromium.org> Commit-Queue: Petro Akzhygitov <pakzhygitov@google.com> Cr-Original-Commit-Position: refs/heads/main@{#1135881} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4480870 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/5735@{#34} Cr-Branched-From: 2f562e4-refs/heads/main@{#1135570}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm on 10.9.5, and there's no way to watch Netflix or local streaming services like Flow. I guess this is because of Widevine. Is there a way to do it?
Thanks!
The text was updated successfully, but these errors were encountered: