Immigration to introduce 90 day reporting online

[Big Boy]

Yes, it's really painful. Over 20 attempts now - I've stopped counting. I've seen this problem many times with MOD's programmers back in the 90's. It's a stupid locking problem, which should be highlighted at a much earlier stage.

Failure message is less than helpful. Why do they waste everybody's time demanding a page full of info before telling you that you've failed to get 'the' slot?

[Pleng]

You could perhaps try an form auto-fill addon for your browser?
A quick google search found the following available for firefox. I'm sure other browsers have them too.

https://addons.mozilla.org/en-US/firefo ... fillforms/
https://addons.mozilla.org/en-US/firefo ... ll-262804/

[Homer]

What a pain. But it worked. I'll know in a day or 3 if it worked on their end.

Both tries used Chrome browser (latest version 48.0.2564.116 m (64-bit)) on a fast computer with 8gb ram running Win 7.

First try used User-Agent Switcher for Chrome (latest version 1.0.43) set to Internet Explorer 10. None of the dropdowns worked on page 1 of the input form, or maybe I didn't wait long enough.

Second try, Chrome without user agent switcher. Dropdowns worked.

On both first and second try the page kept communicating with the server. On the tab, the refresh symbol (the curved arrow) and something else (my memory.....) flashed rapidly. That' ain't right. After they stopped flashing the form was ready for input. Click on a field or type and wait as the flashing began again. Slowly, very slowly, with numerous requests from Chrome if I wanted to either wait or kill the page, a field was ready for input. I got to submit, clicked and waited. From page 2 on everything was fine.

[Ratsima]

The software is written using an 'onkeyup' in every field of the form (at least on the first page). So that means that it checks the data in the field on every keystroke. That's why it's so unresponsive. I have no idea why anyone would use this sort of strategy on this sort of form. It makes no sense.

[PeteC]

^ It's very possible they don't want it to work well. If it was normal and efficient and everyone used it, what would they do with the bloated ranks of regional immigration police clerks? At the moment they've fulfilled their promise/announcement to have it, no more than that. Pete

[Ratsima]

Well, there are certainly easier ways to sabotage a website. Someone went to great effort to write volumes of useless code. My guess is they handed the task to some bigwig's relative who just completed an online course in HTML.

[Homer]

The software is written using an 'onkeyup' in every field of the form (at least on the first page). So that means that it checks the data in the field on every keystroke. That's why it's so unresponsive. I have no idea why anyone would use this sort of strategy on this sort of form. It makes no sense.

In 18 years as a software developer, never heard of anyone validating after each keystroke, but I've debugged code so bizarre I'm certain it exists. But I don't understand how that that sort of validation, in and of it self, would cause the flurry of server round trips. There are many ways to do that.

A story of interest only to software developers. In '96 I was on a team of experienced FoxPro developers when the next version appeared with a central Event Loop handler. We were told in no uncertain terms we had to use the Event Loop for certain common tasks and our code would be check for compliance. After training, we were given some simple tasks to do in an afternoon. It broke some team members brains. After the team leader demanded to see the progress of those who hadn't volunteered their work for scrutiny, we got to see apps that, after being clicked, blinked ... and blinked ... and blinked ...

[Homer]

What a pain. But it worked. I'll know in a day or 3 if it worked on their end.

Received the confirmation email 3 hours later. Whoo hoo!

[Ratsima]

But I don't understand how that that sort of validation, in and of it self, would cause the flurry of server round trips. There are many ways to do that.

They use Ajax to validate some fields without the user having to submit the form. That may account for some of the server round trips.

Here's a sample of the onkeyup usage:

Code: Select all

	
	<input type="text" id="birthYear" name="birthYear" maxlength="4" style="width: 40px" 
	onkeypress="return onKeyPressAllDigit(event, false)" 
	onkeyup="if(this.value.length==0){$j('#birthMonth').focus();}" 
	onblur="setFullDate();"> (DD/MM/YYYY) 
	<input type="hidden" name="pg1_1FormBean.birthDateStr" value="">

I can't be bothered to plough through it anymore. It's completely undocumented. No comments whatsoever. I certainly wouldn't want to try and maintain it.

[Big Boy]

Well, after dozens of failed attempts this time, I made the dreaded journey to Soi 19 today. Arrived at 10:00 and on my way home at 10:50, so not as bad as I expected. I must have spent a lot longer trying to get the online version to work.

[dundrillin]

I have a retirement visa and a multlple re- entry permit. My 90 day reporting date is March 13 however I fly to Myanmar on the 5th of March returning to Thailand on the 14th. Do I still have to attend immigration here in HuaHin or will the visit to Myanmar suffice?

[buksida]

Your 90 days will start again when you return to Thailand on the 14th so no need to do it.

[dundrillin]

Thanks for your very quick and helpful response.

[hhinner]

Any TM30 reporting requirement at HH immi for such trips as dundrillin's?

[buksida]

No surprise, still no joy out of the immigration "website" 3 months down the line. Another 4 hours wasted for a 30 second job in an empty immigration office.