A couple of years ago I had a long-going discussion with a couple of forum member, including Alex, concerning the online bug which meant that certain CSS rules were not being triggered on resume of a saved online game.

Alex acknowledged the bug and suggested I create a Github ticket. I did this and several several months later received an email to say it had now been fixed.

I'm now considering having another attempt at making a small, traditional TA in Quest, but wanted to check the save/resume issue before I put any work in, and find that nothing has changed. I hide the border and background for the input box in my games, but on resume of a save the CSS isn't being read and the input box border pops up in a glaring white.

In that Alex doesn't appear to be bothering with Quest these days, does anyone have any idea where we are on this bug? Failing that, how I get hold of Alex?

I get notifications from GitHub and I regularly check this forum.

Check you're calling the script in InitUserInterface so it actually gets applied when a game reloads.

If that's still not working, please add something to the GitHub issue to help reproduce the problem. At the very least a link to the game, or attach the .aslx file. Even better, a barebones .aslx file that only demonstrates the issue without the rest of your game stuff in there.

Hi, Alex. Sorry for my assumptions there, but it stems from your lack of input here. I know we all have real lives to lead so I fully understand and my comment wasn't meant as a criticism.

It's been a long time since I worked on this game and I had an awful lot of help with it, so the following doesn't really mean much to me. Anyway, the game I just uploaded to test the resume bug with, has this in the InitUserInterface:

JS.setCommandBarStyle (GetCurrentTextFormat("") + ";border:" + game.defaultbackground)
JS.eval ("$('#status').hide();")
JS.SetBackgroundCol ("black")
JS.eval ("$('#txtCommandDiv').prepend('> ')")
JS.OutputTextNoBr (game.css)
OutputTextNoBr (game.css)
request (SetInterfaceString, "TypeHereLabel=")
if (GetBoolean(game, "inprogress")) {
}
else {
  game.inprogress = true
}

The link is here: http://textadventures.co.uk/games/view/fnn_yl1r_ui81gcnnqrrvq/aftermath

Any updates on this, Alex?

No.

It's not even been 2 days!

Also you haven't added anything to the GitHub issue to help with reproducing this. I know you've pasted a code block on this forum but that's the kind of thing that will quickly be forgotten as it's not even linked from GitHub. Add it to the GitHub issue. Attach a file so that somebody who looks at the issue can immediately reproduce the problem.

I wouldn't know how to attach a file so I'll just add the above to the issue at GitHub. Thanks.

I assure you, Alex, this is not a case of me pestering, but may I ask if you think this bug is likely to get fixed?

I only ask because I'm eager to start on a game, but am reluctant to do so because of the work involved in doing so, if the issue isn't going to get fixed.

I know it may seem trivial to everyone else, but it's a game killer for me.