New issue
Advanced search Search tips

Issue 796363 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 12
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 677022



Sign in to add a comment

Clear raw bytes in MatchPreload(), not in NotifyFinished() for unused preloads

Project Member Reported by hirosh...@chromium.org, Dec 19 2017

Issue description

Currently, for CSSStylesheetResource:
ClearData() is called in NotifyFinished().
After that, only the decoded string is held.

This is blocking Issue 677022, which requires raw bytes (for
subresource integrity) even after NotifyFinished() for unused preloads.

This CL tracks efforts to adjust the ClearData() timing, i.e.
call it in the latter of NotifyFinished() or MatchPreload().
I'll create a doc later.

In a longer term, if this approach is reasonable, we can apply the
same to ScriptResource and thus unify the raw bytes/decoded string handling in ScriptResource and CSSStylesheetResource.

For ScriptResource:
ClearData() is called when SourceText() is called,
which is after NotifyFinished().
After that, only the decoded string is held.

This is needed to allow ScriptStreamer to work on raw bytes if it is before SourceText() call.
If we can make ScriptStreamer to work with decoded data directly (I'm also preparing experimental CLs), then we can also ClearData() at the same timing of "the latter of NotifyFinished() or MatchPreload()".

 
Status: WontFix (was: Started)
Because of its complexity, we abandoned this approach, and are now seeking simpler ways. Closing as WontFix.

Sign in to add a comment