Peculiar results on URL highlight attempt

[K1200]

I set out to write a script (to run when exiting a text field) to locate and highlight any URLs in the text. Ideally, it would highlight the entire URL -- but I resolved to simply locate and colorize the “http:/” portion as a first step. What I’ve encountered are two data cases that I don’t understand.

On the highlighting, the first “run” of the script works as expected. But selecting the same field contents a second time -- or selecting different contents -- results in what I will call color overrun. The entire field gets colorized by some mechanism.

In my testing, I noticed another odd occurrence in that a popup selection duplicates any second occurrence of the ampersand character. What is stored in the field is correct, but the user would be concerned by the displayed choices.

Any insights will be appreciated.

OddCase.fp7.ZIP

[comment]

This is a bug - but it has nothing to do with scripts, script triggers or Substitute().

Quite simply, if you:

1. Apply any formatting to the first character of a text field;

2. Select any value from a drop-down, pop-up or radio button;

the previously applied formatting will now extend to the entire field. The same thing will happen if you enter the field, select all and start typing.

---

I haven't noticed any duplication of the ampersand character in your file.

Edited March 14, 2009 by Guest

[K1200]

I haven't noticed any duplication of the ampersand character in your file.

I've attached a screen capture of the repeated ampersand. If you not seeing it then I'm led to believe it only occurs on PCs -- hopefully not just my PC. [color:green]I will appreciate anyone's confirmation of this phenomena.

Regarding the highlighting, is it a bug only in 10.0? Although I didn't try this exact technique, I don't recall seeing anything like in during two years of using 8.5.

Thanks for your help.

[comment]

is it a bug only in 10.0?

I have tested this in v.7 and 8.5 and it behaves the same way.

I don't recall seeing anything like in during two years of using 8.5.

Neither do I, but I am not really surprised - there always was an issue with the invisible 'start' and 'end' formatting tags.