My experience suggests that the script is trying to load a resource (Possibly a sticker graphic), is failing because the resource is unavailable or not being served within the timescale the script is expecting, and is producing the message for user/developer reference. My quick-fix suggestion would be for the routine in question to be identified and re-coded to only show the error if a debug flag (i.e: debuglocal=on) is present in the page URL - Meaning devs can still see these by adding that parameter to the page URL by hand, whilst users will no longer see it pop-up as they havn't "Opted-in" to debug output. :-)
Hope this is useful! :-) +++ ThunderDragon +++
WARNING: The "Always On" GoodyBag does NOT offer unlimited data. More details Here.
i before e except after Firefox... German Sausage jokes: They're the Wurst!...
Hi @gsklb04 Thanks for your input, yes I'm aware of the Lithium problems and all the inconvenience you and your good lady wife have suffered amongst many others. Hopefully base upon Alex's latest update things should start to improve albeit knowing Lithium slowly. This error message for me however is new. @thunderdragon, @t_will Thanks Thunderdragon for you insight. It does seem that this has to do with the stickers, I believe as when I get this message the stickers fail to load in that thread. It seems when a new feature is introduced it is accompanied by a new problem.
Hi guys this is the problem I brought up in GD, I’m using chrome on my iPad, it’s a right pain in the but, also there’s another message crops up about giffgaff diverting too many times and to get back on I have to clear my cache and log back in, this happens several times a day 😡
Apparently in another thread related to device compatibility alex_w has acknowledged that this is due to a bug with the stickers which is being worked on. I would have preferred the stickers be removed until the problem is resolved and fully tested, but it seems that is not the giffgaff way.