- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Mar 2017 17:36:16 +0000
- To: public-css-archive@w3.org
@bzbarsky raised the issue of what to do with `<object>`, which is technically a submittable form element, but is non-replaced when falling back, and also should probably be handled consistently with `<video>` in any case. Options are: 1. explicitly declare non-replaced fallback of replaced elements to be treated as `display: none` 2. clarify that non-replaced fallback of replaced elements is still treated as non-replaced, and make `<object>` an exception to the form controls rule 3. clarify that non-replaced fallback of replaced elements is still treated as non-replaced, and have `<object>` be inconsistent with how fallback is handled for `<video>` and `<canvas>` 4. give up and try the “all of these things just display their DOM contents and lose their special rendering” option mentioned above See minutes from the currently-active resolution on this issue here: https://lists.w3.org/Archives/Public/www-style/2017Mar/0001.html -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/540#issuecomment-285423025 using your GitHub account
Received on Thursday, 9 March 2017 17:36:28 UTC