The Trainline
in [UK Mac]
|
From: Nigel Coke-Woods on 29 Dec 2005 08:30 I just tried to book a ticket on the Trainline using Safari. Pressing "buy ticket" did nothing. The support guy on the phone could see the booking at his end and knew I was using Safari. He told me exactly what to do, which was to turn off Javascript, and how to do it. So far 10/10. The booking went through, and then I asked him "why did I have to turn off javascript?" His answer was "because Safari does not have enough memory due to changes made to Safari." And he was doing so well up until then. As to whose Javascript is faulty, Safari or Trainline, I couldn't say. Nigel -- Rev. Nigel Coke-Woods, Methodist Minister You can email me via the website at http://www.coke-woods.co.uk AIM/iChatAV: cokery
From: DrewM on 29 Dec 2005 11:55 Nigel Coke-Woods wrote: > I just tried to book a ticket on the Trainline using Safari. Pressing > "buy ticket" did nothing. The support guy on the phone could see the > booking at his end and knew I was using Safari. He told me exactly what > to do, which was to turn off Javascript, and how to do it. So far 10/10. > The booking went through, and then I asked him "why did I have to turn > off javascript?" His answer was "because Safari does not have enough > memory due to changes made to Safari." And he was doing so well up until > then. As to whose Javascript is faulty, Safari or Trainline, I couldn't > say. Safari's JavaScript and DOM capability isn't quite up there with the likes of the latest Firefox, but I can't imagine anything Trainline might be doing to that would be pushing its limits. Sounds like poor implementation from Trainline. At least it degrades properly with JavaScript turned off. drew.
From: Woody on 29 Dec 2005 12:18 DrewM <callmedrew(a)gmail.com> wrote: > Nigel Coke-Woods wrote: > > > I just tried to book a ticket on the Trainline using Safari. Pressing > > "buy ticket" did nothing. The support guy on the phone could see the > > booking at his end and knew I was using Safari. He told me exactly what > > to do, which was to turn off Javascript, and how to do it. So far 10/10. > > The booking went through, and then I asked him "why did I have to turn > > off javascript?" His answer was "because Safari does not have enough > > memory due to changes made to Safari." And he was doing so well up until > > then. As to whose Javascript is faulty, Safari or Trainline, I couldn't > > say. > > Safari's JavaScript and DOM capability isn't quite up there with the > likes of the latest Firefox, but I can't imagine anything Trainline > might be doing to that would be pushing its limits. > > Sounds like poor implementation from Trainline. At least it degrades > properly with JavaScript turned off. How could you possibly sugest that anything could be wrong with that work of pure genius that is the trainline website could be anything other than perfect? Don't you realise that taking something as simple in concept as getting a train ticket into something which is slightly slower than phoning who lives within a mile of a train station to go down there and ask someone is a skill that doesn't come easily? -- Woody Alienrat Design Ltd
From: Andy Hewitt on 29 Dec 2005 12:37 DrewM <callmedrew(a)gmail.com> wrote: > Nigel Coke-Woods wrote: > > > I just tried to book a ticket on the Trainline using Safari. Pressing > > "buy ticket" did nothing. The support guy on the phone could see the > > booking at his end and knew I was using Safari. He told me exactly what > > to do, which was to turn off Javascript, and how to do it. So far 10/10. > > The booking went through, and then I asked him "why did I have to turn > > off javascript?" His answer was "because Safari does not have enough > > memory due to changes made to Safari." And he was doing so well up until > > then. As to whose Javascript is faulty, Safari or Trainline, I couldn't > > say. > > Safari's JavaScript and DOM capability isn't quite up there with the > likes of the latest Firefox, but I can't imagine anything Trainline > might be doing to that would be pushing its limits. > > Sounds like poor implementation from Trainline. At least it degrades > properly with JavaScript turned off. It is. I've used the trainline site for years to book tickets for my Mum. It's *never* worked in Safari - you usually don't see the select boxes for the journeys. FWIW, they also don't show the cheapest available tickets online either, it's actually better to phone for a ticket - or call into a station. -- Andy Hewitt ** FAF#1, (Ex-OSOS#5) - FJ1200 ABS Windows free zone (Mac G5 Dual Processor) <http://andyhewitt.webhop.net/> (updated Nov. 2005)
From: Bonge Boo! on 29 Dec 2005 12:49 On 29/12/05 17:18, in article 1h8cd89.19eddxs1edb85cN%usenet(a)alienrat.co.uk, "Woody" <usenet(a)alienrat.co.uk> wrote: >>> I just tried to book a ticket on the Trainline using Safari. Pressing >>> "buy ticket" did nothing. The support guy on the phone could see the >>> booking at his end and knew I was using Safari. He told me exactly what >>> to do, which was to turn off Javascript, and how to do it. So far 10/10. >>> The booking went through, and then I asked him "why did I have to turn >>> off javascript?" His answer was "because Safari does not have enough >>> memory due to changes made to Safari." And he was doing so well up until >>> then. As to whose Javascript is faulty, Safari or Trainline, I couldn't >>> say. >> >> Safari's JavaScript and DOM capability isn't quite up there with the >> likes of the latest Firefox, but I can't imagine anything Trainline >> might be doing to that would be pushing its limits. >> >> Sounds like poor implementation from Trainline. At least it degrades >> properly with JavaScript turned off. > > How could you possibly sugest that anything could be wrong with that > work of pure genius that is the trainline website could be anything > other than perfect? Personally I think its wonderful. Never had a problem with it, and if I did have a problem I just do the normal thing and try another browser. I've been using it since IE5 days on my Mac and its always worked fine; so I'd be more inclined to blame Safari at this point. I travel by train very infrequently, but when I do, 3 mins on thetrainline site and my CC at bath Spa. So damn easy.
|
Next
|
Last
Pages: 1 2 Prev: What does EEventManager do? Next: iPod shuffle - loading without iTunes |