Talk:Superellipse: Difference between revisions

::::::: I did some cursory (and somewhat shallow) web searching for problems with Chrome, LaTeX rendering --- particularly the &nbsp; <big><nowiki> <math> </nowiki></big> &nbsp; blank/empty rendering, and other such symptoms. &nbsp; There are this and other problems that have been introduced with a new(er) version of Chrome, some have a work-a-round, but the problems are being addressed (as far as I can glean from the various articles), and, if indeed, the symptoms being seen are manifestations of the same problem(s). &nbsp; I uninstalled Chrome many ages ago when I had similar problems with it's (bad) rendering of various texts and especially some fonts. &nbsp; This latest go-around (here at Rosetta Code) seems to be focused on the "flanking" whitespace and the reversion of changes, and the describing of the symptom of the problem as making the formulae invisible (or more descriptive, the rendering of blanks). &nbsp; Some of the changes being reverted have been around for ''months'', leading me to believe that the problem probably lies with the recent changes to Chrome &nbsp; (and I presume, Safari). &nbsp; I wonder if the mere act of reverting the Rosetta Code pages to an earlier text bypassed &nbsp; (in and of itself) &nbsp; the problem in the newer version of Chrome? &nbsp; I've asked Mr. Hout previously if he reported the problem to Chrome and/or Safari peoples to have this particular problem addressed, and I also requested a bug or tracking number to follow this problem's resolution &nbsp; (nothing replied so far). &nbsp; If Chrome (and/or Safari) doesn't render the LaTeX (or whatever) correctly, maybe the Rosetta Code users of those browsers might be better served if they used FireFox &nbsp; (or <u>any</u> other browser that works) &nbsp; until the problem gets fixed by the code writers of those failing/broken browsers. &nbsp; -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 17:55, 16 September 2016 (UTC)

 

 

:::::::: There is no evidence that the problem lies with Safari and Chrome, and the likelihood of two entirely separate engines having simultaneously acquired identical bugs seems a little too low to really detain us for long :-) The visibility problems are not new. If you really wanted to understand what was going on, you would need to make a careful study of the output of the Wiki software's preprocessor. In the meanwhile, you can retain the value of your edits (changes in visible spacing and font sizing), and remove the damage inadvertently done to visibility in OSX Safari and Chrome (not just recent versions) by reverting the state of the math tag contents alone. There is no dishonour in having unwittingly created a problem - though it might raise an eyebrow or two if you were to resist the repair :-) [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 18:19, 16 September 2016 (UTC)