Originally Posted by xelawho
did you try with the method described in post 21, above?
I don't know why; I don't know how...... but sometimes fate deals a good hand.
( it's rare though )
I actually missed that post (see first remark)...... I guess it was meant to be like that.
After the weekend's work, and Sunday, sort of stupidly releasing a working version (in the heat of the moment). Today saw good housekeeping, leading to 'covering the fundamentals': getting all the declarations right (when a release would have been correct).
There's only a break-line that Chrome doesn't like (actually W3c).
Oh, while I remember re W3c: onhaschange does exist. It's part of a whole new raft of event handlers in HTML5 (what a bugger eh? )
Either way.... I didn't manage to use it correctly.
But leaving all that aside, this really IS the ideal point to move to the next phase.
This morning would have been too early.
Definitely a lesson to be learned there IMHO.
Tomorrow, may well see full automation.
(Thanks for the direction.)