Frame is deprecated from HTML 5

[GoogleCodeExporter]

Hi all,

I am wondering the future of WebAnywhere because a key element in WA -
 'frame' is deprecated in HTML 5. Any comments?

The following elements are not in HTML 5 because their usage affected 
usability and accessibility for the end user in a negative way: 

•frame 
•frameset 
•noframes 

Reference: http://www.w3.org/TR/2009/WD-html5-diff-20090423/

Regards!

Cameron

Original issue reported on code.google.com by hgn...@gmail.com on 27 Apr 2009 at 6:52

[GoogleCodeExporter]

Cameron,

Good question. Even after HTML 5 is published by the W3C as a Recommendation,
browsers will continue to support HTML 4.x and XHTML 1.x documents. Therefore, 
we
don't anticipate any changes to WebAnywhere's interface at this time. That said,
there will be several new features in HTML 5 that we may want to take advantage 
of
for the WebAnywhere interface in the future and we may want to look at the use 
of
iframes instead of frames.

HTML 5 is still an early draft, but as it nears completion, we will add the 
necessary
features for WebAnywhere to handle new HTML 5 elements and attributes.

Does that answer your question?
Best,
--wendy

Original comment by chisholm...@gmail.com on 27 Apr 2009 at 9:14

[GoogleCodeExporter]

Thanks for your reply, Wendy.

I agree with you. And even without frame we can do some hacking in the PHProxy 
like 
injecting some code to the top of a return page.

Cameron

Original comment by hgn...@gmail.com on 29 Apr 2009 at 2:12

[GoogleCodeExporter]

I've responded to this on the new developers mailing list here:
http://groups.google.com/group/webanywhere-dev/

Original comment by jeffrey....@gmail.com on 29 Apr 2009 at 2:23

[GoogleCodeExporter]

Let's open another ticket when it doesn't work with browsers. This should not 
bring
in problems in recent years.

Original comment by hgn...@gmail.com on 2 Jan 2010 at 7:31

• Changed state: WontFix

[GoogleCodeExporter]

Frames have been replaced with iframes as a few revisions ago - I think this
addresses this issue and is cleaner.

I should have marked this as fixed.

Original comment by jeffrey....@gmail.com on 2 Jan 2010 at 3:15

• Changed state: Fixed