Skip to content
This repository has been archived by the owner on Nov 29, 2018. It is now read-only.

Weird issue with the telemetry question, FF 9.0.1, and release 2.16; workaround included #3154

Closed
lukeis opened this issue Mar 3, 2016 · 5 comments
Closed

Weird issue with the telemetry question, FF 9.0.1, and release 2.16; workaround included #3154

lukeis opened this issue Mar 3, 2016 · 5 comments
Assignees
@lukeis
Labels
Browser-Firefox Lang-Ruby Priority-Medium Restrict-AddIssueComment-Commit Status-Duplicate Type-Defect

Comments

@lukeis
Copy link
Member

lukeis commented Mar 3, 2016

Originally reported on Google Code with ID 3154

So all of a sudden, with the 2.16 release, my FF 9.0.1 gets the "Would you like to help
improve Mozilla Firefox by automatically reporting blah blah blah" popup on new windows,
which is fine, except that when that is there click commands are ignored, so tests
can't run.

The following code in the Ruby driver fixes the problem, in as much as with this code
I can click on things in Selenium and all my tests pass:


      profile = Selenium::WebDriver::Firefox::Profile.new
#      profile['toolkit.telemetry.prompted'] = 2
#      profile['toolkit.telemetry.rejected'] = true

      caps = Selenium::WebDriver::Remote::Capabilities.firefox(:firefox_profile =>
profile)
      @driver = Selenium::WebDriver.for( :remote,  :url => "http://localhost:#{@port}/wd/hub",
                                        :desired_capabilities => caps)

Note that this amounts to "run with an explicit profile"; the profile doesn't actually
have to have anything in it.  The telemetry request is still there, it just doesn't
block clicks anymore.

If you uncomment the two commented lines, those values *are* set; "about:config" shows
them as set.  It just doesn't stop the request from popping up.

-Robin

Reported by robinleepowell on 2012-01-05 23:56:52
@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by ajaykemparaj on 2012-01-06 09:19:19

  • Labels added: Browser-Firefox, Lang-Ruby

@lukeis lukeis self-assigned this Mar 3, 2016
@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

I was about to report the same problem, but for the C# client bindings.

It looks like this is closely related to issue 3144.

Unfortunately the workaround doesn't work for me. Having read issue 3144, and the firefox
issue it linked to, I haven't been able to get any combination of profile preference
settings to allow click commands, or dismiss the telemetry prompt.

If I've understood it correctly, setting 'toolkit.telemetry.prompted' to 2 should prevent
the prompt altogether. To simulate the user having previously clicked no at the prompt,
the 'toolkit.telemetry.enabled' preference should be set to false and the 'toolkit.telemetry.rejected'
preference should be set to true. Hence I have the following code when I create my
capabilities object:

var profile = new FirefoxProfile();
profile.SetPreference("toolkit.telemetry.prompted", 2);
profile.SetPreference("toolkit.telemetry.enabled", false);
profile.SetPreference("toolkit.telemetry.rejected", true);
capabilities.SetCapability("firefox_profile", profile.ToBase64String());

As mentioned though, this still results in the prompt being displayed, and click commands
being ignored.

As it happens, I've discovered that reverting back to v2.15 allows my tests to work
correctly with Firefox v9.0.1, so I'll be doing that until this issue can be resolved.

Reported by ben.adderson on 2012-01-06 13:13:50

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by dawagner on 2012-01-06 14:22:15

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016 

The same issue is occurring for me using v2.19 using the exact same telemetry settings
(2, false, true) in Python.  The message still displays.

Reported by totoman67 on 2012-03-12 19:13:57

@lukeis
Copy link
Member Author

lukeis commented Mar 3, 2016

Reported by luke.semerau on 2015-09-17 18:14:31

  • Labels added: Restrict-AddIssueComment-Commit

@lukeis lukeis closed this as completed Mar 3, 2016
@SeleniumHQ SeleniumHQ locked and limited conversation to collaborators Mar 4, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lukeis lukeis

Labels
Browser-Firefox Lang-Ruby Priority-Medium Restrict-AddIssueComment-Commit Status-Duplicate Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lukeis