Enhancements in this build:
- added new Margolus THEME
- added new Margolus alias
- fixed a tile boundary issue with Margolus rule
Code: Select all
patterns in the forums on Internet Explorer are fine until you click "Show in Viewer", but then they reset the view to the top of the page.Just fixed it. I'll release it shortly.dvgrn wrote:Looks like some recent build must have made Internet Explorer unhappy.
Just noticed something odd about Build 396, from trying to open an oversized pattern in an old thread.rowett wrote:Build 396 is now available on the lazyslug server...
This has been fixed for the next build. Nice catchdvgrn wrote:Just noticed something odd about Build 396, from trying to open an oversized pattern in an old thread
Hmm, can't think of anything offhand -- especially since if recent history is any guide, you'll be on to Build 401 before there's very much time to savor Build 400.rowett wrote:Any special requests for Build 400?
Highly likely. I noticed a shorter release cycle gets better engagement from forum members. Plus if (when) I do break stuff I can normally fix it within 24 hours.dvgrn wrote:... you'll be on to Build 401 before there's very much time to savor Build 400.
Nothing rings a bell. But if it's working now I'm happy!dvgrn wrote:There was a regression bug that started bugging me a few weeks ago, but now it seems to have gone away again. Did you re-fix anything having to do with STOP not working when the stop time wasn't a multiple of the step size?
dvgrn wrote:Thanks for the details! I can't see any behavior that's anything like this, no matter which browser I use. My OS is also Windows 10, so I'm fairly puzzled at the moment.Saka wrote:Hi again, I don't know if it was ever fixed, but the giant JavaScript wall of text still appears on my PC at the top of every page. It also does not appear on my phone and LifeViewer on the article pages work just fine on my phone.
As usual I can see the LifeViewers on the home page of this site just fine with no wall of text.
My OS is Windows 10 Pro Version 1903, OS Build 18362.356
I am using Google Chrome Version 76.0.3809.132 (Official Build) (64-bit)
Additionally, I tested it on Microsoft Edge 44.18362.329.0 with Microsoft EdgeHTML 18.18362 (Whatever that is...) and the wall of text still shows.
The text wall also shows in Firefox 66.0.3 (64-bit).
Could this be an OS-specific problem?
Heres the text wall on all 3 browsers (Left: Chrome, Right:Firefox, Middle: Edge)
However, I'm far from being a Javascript expert, and I can imagine all kinds of weird things that could go wrong -- e.g., if for some reason your system didn't allow Javascript to load completely if it's over a certain size. LifeViewer is getting pretty big.
In your walls of text, can you read LifeViewer's code all the way from the beginning
//<![CDATA[ var da="function"== ...
to the closing
... "POPUPWIDTH",bj:"POPUPHEIGHT",Yc:"#"}; //]]
? Or is some of it going missing, and therefore the wall of text is popping up as an attempt to show the error?
Maybe an interesting detail: the part of the wall of text that's being displayed is
\n\n'), h.document.close(), etc. -- but the actual LifeViewer Javascript in that area looks like this:
So the text </html> is mysteriously going missing from the h.document.write call that has to do with opening a separate Image window. If that's happening at that point, then I suppose other things may be getting removed elsewhere -- at least in this wall-of-text copy of LifeViewer that's being printed at the top.Code: Select all
height="'+a.s+'" src="'+b+'" alt="'+k.mn+'"/>\n\t</body>\n</html>\n'), h.document.close(),a.g.notification.F("Image Captured",300,!0)):a.g.notification.F("Could not open Image window!",k.vm,!0)}
Just to be clear, when the wall of text appears, you can't scroll down to a working LifeViewer -- right? Might you have some kind of aggressive anti-virus program installed on your PC, that prevents HTML/script injection attacks by removing suspect HTML tags from "untrustworthy" web sites -- or something like that?
(I'm almost certainly barking up the wrong tree here -- for all I know, the "\n\n" display is supposed to be happening for some reason or other -- but, hey, at least it's a theory.)