Anonymous user
Talk:Superellipse: Difference between revisions
m
→Formulae now invisible on standard OS X browsers: added comments about shared browser code.
No edit summary |
m (→Formulae now invisible on standard OS X browsers: added comments about shared browser code.) |
||
Line 17:
:::::::: 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)
::::::::: Safari and Chrome are not two ''entirely'' separate engines; WebKit is an open source browser engine for rendering web pages that is used in Safari and it had been used in Chrome, but Google currently incorporates (I don't know the date) a WebKit fork/offshoot of WebKit with software named "Blink", so there is some commonality of code, of which and how much, I do not know. I don't know enough about Wiki's software pre-processor or even where to find/view the output of same, let alone make a careful study of its output, nor would I suggest that someone study that as a means of resolving a problem (or trying to find out the location of where the problem is). That is way beyond my capabilities and time availabilities. Since I don't see the non-rendering (the "invisibility" that you see) with the web-browsers that I have installed), it wouldn't behoove me or Rosetta Code to make further changes in removing whitespace in specific areas as I can't see the results (the failures) that you're seeing with your browsers). I don't believe that I introduced (even unwittingly) a problem, but as I see it, you most likely have uncovered a problem in the way LaTeX is rendering whitespace in the browser(s) that you're using. I'll never accuse anyone of introducing a problem just because my browser fails in handling (rendering) whitespace. I've been web-searching for Chrome's (rendering of LaTeX and other stuff) problems, and there seems to be enough discussion on issues related to these types of issues. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 18:53, 16 September 2016 (UTC)
| |||