Live Region - Nested Live Regions ("assertive" inside of "off")

Important: This case is not defined in the spec. The "Summary" and "Description of the expected behavior" are based solely on what I feel makes the most sense.

Summary: There is one live region on this page which contains two live regions inside of it on this page. The mainLiveRegion has live="off". The first subregion, myLiveRegion1, has no live property specified; therefore it inherits the "off" property from its parent. The second subregion, myLiveRegion2, has live="assertive"; therefore it should be treated as a live region that is "assertive", despite its parent's live="off" setting. The rule here is that the closest live=X setting wins. This will make things easier on web developers as they only need to consider the liveness of a particular element without needing to think through its entire chain of parents. This solution is also rather elegant since it keeps the entire system of using live=X logically consistent. Since the live="off" property is the default if nothing is specified, one can argue that the main BODY element of an HTML page which does not have a live=X property is "off". If that is the case, then having the closest live=X setting win is an idea that naturally follows from our expectation that live="assertive" will make a SPAN element "assertive" under a BODY which is "off".

Description of the expected behavior: After presenting the heading, the user agent should present the text in each of the live region areas at the time. After presenting the "Important" note, it should then proceed to the "Summary" section followed by the "Description of expected behavior" section. It should then continue to read the filler text until the end of the document and stop. Updates to the first live region should be ignored as the first live region inherits live="off" from the mainLiveRegion since it does not have a live=X of its own. However, updates to the second live region should be announced as soon as possible as it is "assertive".

The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should.

The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should.

The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should. The filler text is here to let developers run their user agents for a longer period of time to make sure that everything will continue to behave as it should.