New issue
Advanced search Search tips

Issue 600383 link

Starred by 3 users
Status: WontFix
Owner:
jkarlin@chromium.org
Closed: Jan 15
Cc:
shivanisha@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

migrate doc.write script blocking from blink Settings to RuntimeEnabledFeatures

Project Member Reported by bmcquade@chromium.org, Apr 4 2016 
blocking of scripts loaded via document.write is currently controlled by blink Settings. In hindsight, this should be using RuntimeEnabledFeatures instead. We should migrate from Settings to REF.

Proposing that we target fixing this for M52 timeframe.

Comment 1 by bmcquade@chromium.org, Apr 6 2016

Status: Assigned (was: Untriaged)
Based on additional discussion, it's not 100% certain that we should make the change. We should first evaluate to make sure there are no compelling reasons to stay with Settings. If there aren't then I think it makes sense to move to REF for consistency.
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 3 by sheriffbot@chromium.org, Jul 14 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by jkarlin@chromium.org, Sep 9 2016

Cc: shivanisha@chromium.org jkarlin@chromium.org
 Issue 645461  has been merged into this issue.

Comment 5 by jkarlin@chromium.org, Sep 9 2016

Cc: -jkarlin@chromium.org
Owner: jkarlin@chromium.org
Status: Started (was: Assigned)

Comment 6 by bmcquade@chromium.org, Dec 7 2016

Blocking: -599875
Removing as blocker for 599875. This is related to the doc.write launch, but doesn't block it.

Comment 7 by benhenry@google.com, Jan 11 

You started fixing this bug over two years ago. Are you still working on it? You can update the status to "archived", "wontfix", or "closed". You can remove yourself as owner and change status to "untriaged", but if this is still a real bug, please do not sit on it.

Comment 8 by jkarlin@chromium.org, Jan 15

Status: WontFix (was: Started)
Wontfix as this is launched and REF is unnecessary at this point.
►

Sign in to add a comment