no need to make that sentece less technical.1- framesets or inline frames are objects that can contain web elements newly opened.
for example:www.nvaccess.org is holder of a webpage called 'homepage'. within that webpage, there is need to open and process a webpage from facebook.com for specific cookies retained from any client. then while homepage is open, the frameset trys to gather elements from facebook.com as mentioned above. then assume that another inline frame is embedded within that frameset which i said in this example. NVDA no longer does not presumes that frameset which is inside, an object which requires new browse mode. this frameset is presumed a real part of container frameset and does not require NVDA to present a new browse mode interface. this is my mind however.
On 26.09.2014 13:18, James Teh wrote:
Hmm. I think we need to reword that entry (even in English) to make it less technical. :)Jamie On 26/09/2014 7:14 PM, Fatma Mehanna wrote:hi all, in rev10436, there is a line about framesets: +- In Internet Explorer and other MSHTML controls, framesets inside framesets no longer cause a new browse mode document to be created for the inner framesets, which was not allowing navigation to outer frames. (#4418) how can i convey the meaning of this line simply? thanks.
