1) In your 3-alert example, i noted exactly what i expected; no match on the first two which is correct, and a match on the last.
I think you may be alluding to my assumption that the GET will return, at minimum, the "images/CodatronP4.png" (where the page number is from 1 to 7) AND that (perhaps) may be incorrect.
I look at it this way, in the HTML document, that string is exactly what is "in" src so the possibility is essentially zero.
And if by some remote chance and SNAFU of a mobile browser, it gets trashed, then the whole page at that point becomes non-recoverable, a user cannot be assumed to have any intelligence.
Thanks to you, i now know three ways to get a cat out of its skin
Using substring() makes it read better,but why in heck was the syntax of JS made to be so non-conforming to standards set by the first real languages like Cobol, Fortran and Algol?
At least charAt() is not messy and looks good as well.
Oh my! That last example is SOOooooo _SIMPLE_ and neat and ...