On Feb 2, 6:12 pm, Anthony Lieuallen <[email protected]> wrote: > New UI: > 1) Select script > 2) Click edit > 3) Type the URL (and "// @include ")
> Can you describe _why_ you think the new UI is harder to use? I can describe why it's much harder for me. I have a few scripts that don't have any @includes at all. They could work anywhere. I used the interface to set up the domains on which I want them to be used (opt- in style). Now I just lost all my configured domains on them because while poking around for how to get that UI to pop up I hit edit. In desperation I added a single @include rule, which then apparently deleted all my previously configured includes that were not stored in the script and replaced it by this one rule without warning. So I reverted my profile to a backup. Also, I update any of these scripts I now have to remember to copy my old set of includes and paste them into the new one. I'm sure it wasn't intended this way, but to me you removed a major piece of functionality without a valid replacement. -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.
