- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Thu, 16 May 2013 16:15:25 -0600
- To: <public-multilingualweb-lt@w3.org>
- CC: "'Silvia Pfeiffer'" <silviapfeiffer1@gmail.com>, 'Pēteris Ņikiforovs' <peteris.nikiforovs@tilde.lv>, <public-html@w3.org>
> I'll try to go through the elements today and come with a possible > list a ambiguous cases and proposed defaults. Here it goes: Those three elements should probably be within-text='nested': <script>, <iframe>, <noscript> I would tend to say <textarea> may also be within-text='nested'. There are a few elements that are clearly within-text='yes' but may contain non-phrasing content. For example <select> can have <option>. So we end up with a non-within-text element inside a within-text element. I see two way to address those: a) Do nothing. Just report each element as it is. or b) Say that elements not within text that are inside of element within text must default as 'nested'. I would tend to go for a) (not say anything). For all others I would default on within-text='yes', knowing that there are some occurrences where 'nested' would be better. Three elements especially: <math>, <svg> and <canvas> have good arguments to be within-text='nested', but I think we still would be better with defaulting to within-text='yes'. The bottom line is that for many elements there is no way 'right' choice. But overall it usually hurts less to have sub-flow text inside another flow than to have non-sub-flow text cut out from its context, so erring on within-text='yes' is probably better. -ys
Received on Thursday, 16 May 2013 22:16:03 UTC