- From: John J Barton <johnjbarton@johnjbarton.com>
- Date: Thu, 9 Feb 2012 10:10:48 -0800
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: public-webapps@w3.org
On Thu, Feb 9, 2012 at 10:01 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 2/9/12 12:43 PM, John J Barton wrote:
>>>
>>> The drawback is that your fallback behavior in UAs without support for
>>> the
>>> new feature is quite different. Is that a problem? Developer feedback
>>> definitely needed there.
>>
>>
>> Extending the API on iframe would make fallback easy even though it
>> lacks elegance:
>> if (iframe.port) {
>> // modern browser
>> } else {
>> // we still deal with contentWindow carefully for old timers
>> }
>>
>
> The fallback issue I was talking about is that if you mint a new element
> called <xframe> then it wouldn't even load pages in an old browser.
Yes, sorry, I did understand that. Let me try again:
If, rather than using <xframe>, we simply add "port" to <iframe> then,
as you implied originally, there is no fall back problem. Fallback is
as above.
jjb
Received on Thursday, 9 February 2012 18:11:20 UTC