- From: Marcos Caceres <w3c@marcosc.com>
- Date: Sat, 28 Jan 2012 11:45:00 +1000
- To: Scott Wilson <scott.bradley.wilson@gmail.com>
- Cc: public-native-web-apps@w3.org
On Saturday, 28 January 2012 at 07:23, Scott Wilson wrote: > So am I right that we need to make the widget object available in all the child iFrames and Frames of the Widget's start file? Is it *really* necessary? Can't the (i)frame just do "parent.widget"? Both the Widget object is designed to work across both iframes and different tabs (and across different windows). Those cases sometimes apply to widgets, but you are right to say that mostly they don't. However, I think it would be a bad architectural decision to explicitly (in spec I mean) force an Document used in an iframe to refer to its parent unless it really has to: in general, a Document should not know or care if it's and iframe or not. -- Marcos Caceres http://datadriven.com.au
Received on Saturday, 28 January 2012 01:45:33 UTC