Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mozilla.dev.platform
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion Synchronous loading of about:blank
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Boris Zbarsky  
View profile  
 More options Jan 7 2010, 8:38 am
Newsgroups: mozilla.dev.platform
From: Boris Zbarsky <bzbar...@mit.edu>
Date: Thu, 07 Jan 2010 08:38:56 -0500
Local: Thurs, Jan 7 2010 8:38 am
Subject: Re: Synchronous loading of about:blank
Print | View thread | Show original | Report this message | Find messages by this author
On 1/7/10 6:46 AM, Henri Sivonen wrote:

>> Well, that depends on what we're proposing becomes synchronous.  An
>> actual load of about:blank needs to fire all sorts of events
>> asynchronously (load, pageshow, etc, etc).  Creation of the DOM could be
>> appropriately synchronous as needed, I suppose....

> I was thinking the DOM creation would be synchronous whenever a docshell
> is asked to load about:blank but the events would be asynchronous.

We could try to fake this, but it would be a huge pain involving some
pretty fragile code... in particular, some of those async events
typically come before any DOM creation, and we'd need to hack those
codepaths.

>> Another option might be to just create an about:blank viewer in all
>> cases as soon as a window is created instead of doing it lazily.  If no
>> one does anything with the window before the "real" thing loads, we'll
>> just throw it away, and if someone does do something with it it's no
>> different from now.  I'd somewhat support this approach, actually.

> How would this interact with e.g. the frame loader still wanting to tell
> the docshell to load about:blank when a frame is created?

Just like it interacts now.  I'm just suggesting taking something that
happens _sometimes_ now and making it happen always, eliminating race
issues.

> because navigation from another URL to about:blank still needs to be supported
> (synchronously per HTML5).

Well, let's get that part of HTML5 fixed.  I see no reason to ever make
loads synchronous, and in particular I see no way to do it safely.

-Boris


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google