Issue metadata
Sign in to add a comment
|
Make midi sysex syncable |
||||||||||||||||||||||
Issue descriptionIn https://chromium-review.googlesource.com/c/chromium/src/+/1196283 we're temporarily making the midi sysex permission unsyncable. This is because as a part of launching permission delegation, we need to perform a migration of some settings. Migrating syncable settings is complicated and it's not critical that midi sysex be syncable. So we're temporarily making it not syncable. This should be reverted 2 milestones after permission delegation has rolled out - which at this stage is approximately M74.
,
Sep 3
The above comments aren't relevant or constructive. Please refer to our code of conduct for contributions: https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md
,
Sep 3
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/76e7b6c7586052e4042c7dbf456e3e0bdcfe6065 commit 76e7b6c7586052e4042c7dbf456e3e0bdcfe6065 Author: Raymes Khoury <raymes@chromium.org> Date: Mon Sep 03 03:48:21 2018 Make the midi sysex content setting unsyncable The migration code for permission delegation is going to touch the midi sysex seting which is currently syncable. Migration code does not run well on syncable settings. To work around this for the time being, we're temporarily making midi sysex not syncable. Bug: 802945, 879954 Change-Id: I36fb0c83fbd823e6c4612a64dce84787080a8732 Reviewed-on: https://chromium-review.googlesource.com/1196283 Commit-Queue: Raymes Khoury <raymes@chromium.org> Reviewed-by: Martin Šrámek <msramek@chromium.org> Cr-Commit-Position: refs/heads/master@{#588324} [modify] https://crrev.com/76e7b6c7586052e4042c7dbf456e3e0bdcfe6065/components/content_settings/core/browser/content_settings_registry.cc
,
Nov 12
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by raymes@chromium.org
, Sep 3