FF 3.7a1pre(Gecko/091030-) not working<Greasemonkey>

[er9]

FF 3.7a1pre(Gecko/091029)  ia availabe.
Geko/091030 is not working.
Geko/091031 is not working.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemonkey-users@...
To unsubscribe from this group, send email to greasemonkey-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[geeknik]

I've been running Minefield, aka Firefox 3.7a1pre for months and
Greasemonkey works just fine.  But you have to realize that Firefox
3.7a1pre isn't even alpha software and nowhere near being beta
software.  Things are going to be broken and it will be hard for any
extension author to keep up with the daily updates that are made to
Firefox 3.7a1pre.  If you don't know this, you shouldn't be using
it. :)


On Oct 31, 11:30 am, er9 <er9g...@...> wrote:
> FF 3.7a1pre(Gecko/091029)  ia availabe.
> Geko/091030 is not working.
> Geko/091031 is not working.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemonkey-users@...
To unsubscribe from this group, send email to greasemonkey-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[blissdev]

When I originally starting using 3.7a1pre about two weeks ago
Greasemonkey was working fine, but within the last week the nightlies
have broken Greasemonkey support for me. The plugin appears to work
fine (interface wise) but the user scripts have no effect.

On Nov 1, 11:22 am, geeknik <brian.carpen...@...> wrote:

> I've been running Minefield, aka Firefox 3.7a1pre for months and
> Greasemonkey works just fine.  But you have to realize that Firefox
> 3.7a1pre isn't even alpha software and nowhere near being beta
> software.  Things are going to be broken and it will be hard for any
> extension author to keep up with the daily updates that are made to
> Firefox 3.7a1pre.  If you don't know this, you shouldn't be using
> it. :)
>
> On Oct 31, 11:30 am, er9 <er9g...@...> wrote:
>
> > FF 3.7a1pre(Gecko/091029)  ia availabe.
> > Geko/091030 is not working.
> > Geko/091031 is not working.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemonkey-users@...
To unsubscribe from this group, send email to greasemonkey-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Anthony Lieuallen]

On 11/04/09 11:04, Jordan A. wrote:
> When I originally starting using 3.7a1pre about two weeks ago
> Greasemonkey was working fine, but within the last week the nightlies
> have broken Greasemonkey support for me. The plugin appears to work
> fine (interface wise) but the user scripts have no effect.

You're probably seeing
https://bugzilla.mozilla.org/show_bug.cgi?id=525560

They've changed something deep in the JS interpreter.  It's probably
really a GM bug.  In effect, it broke our detection of the
latest-available-JS-engine.  They don't seem to want to make this
information accessible.  Not sure why.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemonkey-users@...
To unsubscribe from this group, send email to greasemonkey-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Matt Sargent]

Any chance of adding a Tab Focus option to the GM_openInTab API, since
it's not possible to accomplish this in javascript?


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemonkey-users@...
To unsubscribe from this group, send email to greasemonkey-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[cc-21]

Do you mean adding a parameter to specify target, a la TARGET attribute
for <a> elements? If so, I would like to humbly beg for the same thing.
I've needed it in the past, and am likely to need it again.

On 2009-11-04 13:51, Matt Sargent wrote:
> Any chance of adding a Tab Focus option to the GM_openInTab API, since
> it's not possible to accomplish this in javascript?
>    


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemonkey-users@...
To unsubscribe from this group, send email to greasemonkey-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Kuo Yang]

I need that too.

On Thu, Nov 5, 2009 at 10:19 AM, cc <carlclark@...> wrote:

Do you mean adding a parameter to specify target, a la TARGET attribute
for <a> elements? If so, I would like to humbly beg for the same thing.
I've needed it in the past, and am likely to need it again.

On 2009-11-04 13:51, Matt Sargent wrote:
> Any chance of adding a Tab Focus option to the GM_openInTab API, since
> it's not possible to accomplish this in javascript?
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemonkey-users@...
To unsubscribe from this group, send email to greasemonkey-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en
-~----------~----~----~----~------~----~------~--~---

[Matt Sargent]

No, just a simple True/False parameter that determines if the new tab opened by the API is made the active tab.


cc wrote:

Do you mean adding a parameter to specify target, a la TARGET attribute 
for <a> elements? If so, I would like to humbly beg for the same thing. 
I've needed it in the past, and am likely to need it again.

On 2009-11-04 13:51, Matt Sargent wrote:
  

Any chance of adding a Tab Focus option to the GM_openInTab API, since
it's not possible to accomplish this in javascript?
   
    

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "greasemonkey-users" group.
To post to this group, send email to greasemonkey-users@...
To unsubscribe from this group, send email to greasemonkey-users+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en
-~----------~----~----~----~------~----~------~--~---