Talk:Superellipse: Difference between revisions

(Found the bug. It's not in the browsers.)
Line 48:
:::::::::::: Chrome 53.0.2785.113 (64-bit) has these problems... --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 19:34, 16 September 2016 (UTC)
::::::::::::: The bug is, as theory might have predicted, not in the browsers. It turns out to be in the wiki preprocessor, which for some reason generates an ill-formed image placement tag if redundant flanking spaces are inserted into math tags. See: http://rosettacode.org/wiki/User_talk:Rdm#.22math.22_HTML_tag_not_rendering_properly [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 22:47, 16 September 2016 (UTC)
:::::::::::::: In general, browsers are supposed to ignore syntactically incorrect html. I suppose though there might be an argument whether in this case it is the entire style attribute which is syntactically incorrect because of the missing semicolon in the value or whether it is the vertical-align element which is syntactically incorrect or whether it should be the part of the style attribute from the vertical-align element to the end of the style.
:::::::::::::: Worse than that, though, since this behavior is OS specific, it is not clear whether it is even browser code which is relevant.
:::::::::::::: Anyways, I guess my point is that we have multiple issues occurring here, which makes it problematic to talk about "the" bug.
:::::::::::::: That said, what do we have to do, to fix the wiki preprocessor, to not omit that semicolon? I see several tex preprocessors listed at https://www.mediawiki.org/wiki/Alternative_parsers but I do not know enough about mediawiki to know which of those we are using... --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 02:21, 17 September 2016 (UTC)
6,951

edits