This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7807 - term "new master" can be ambiguous
Summary: term "new master" can be ambiguous
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-05 11:32 UTC by Anne
Modified: 2010-10-04 14:28 UTC (History)
4 users (show)

See Also:

Attachments

Description Anne 2009-10-05 11:32:42 UTC 
Assuming nothing has been cached so far and you open the same URL twice, both URLs will start the "application cache update process". However, for whichever is second in starting this process (can it happen at the same time?) the master resource is no longer "new". (It still needs to be added to the list of pending master entries of course.)

I suppose that dropping "new" would be enough if indeed they always happen after each other.
Comment 1 contributor 2009-10-20 01:15:20 UTC 
Checked in as WHATWG revision r4186.
Check-in comment: Remove the word 'new' in 'new master entry' throughout the spec.
http://html5.org/tools/web-apps-tracker?from=4185&to=4186