This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
AT products that rely on the DOM will need to watch for this behavior. Please specify what events are fired in when the an iframe is changed from seemless to not seemless or visa versa.
The spec doesn't specify any special events to be fired, so the only event fired is a mutation event, like for all attribute changes.
mass-move component to LC1
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: <http://dev.w3.org/html5/decision-policy/decision-policy.html>. Status: Rejected Change Description: no spec change Rationale: Mutation events are out of scope for HTML.
moving to API mapping
What is iframe seemless attribute?
(In reply to comment #5) > What is iframe seemless attribute? http://www.w3.org/html/wg/drafts/html/master/single-page.html#attr-iframe-seamless
Not sure I understand a need for AT to be aware about seamless attribute but if they need then it could be exposed as object attribute in case of IAccessible2/ATK, when changed then object_attribute_changed event should be fired.
Resolving this as no longer relevant since iframe[seamless] has now been dropped from HTML: https://github.com/whatwg/html/commit/1490eba4dba5ab476f0981443a86c01acae01311