Cookie problem

[capoaira]

New PR which includes also the old dashboard and a bit cleaner code
The following will change by this PR:
Add a Settingsbutton to the

• Old Dashboard on geocaching.com (https://www.geocaching.com/my/default.aspx)
  

• New Dashboard on geocaching.com (https://www.geocaching.com/account/dashboard)
  

• Profil on opencaching.de (https://www.opencaching.de/myhome.php)
  

The Settings:

The infotext will not be show by default. Only if you click on the ?-Button

@Lineflyer, please test it

[cgeo-ci-bot]

Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
           

See the complete overview on Codacy

[Lineflyer]

Will test it on master and merge to release once tested.

For my understanding:

• The script should work as before on Firefox and on "unaffected" Chrome
• With the problematic Chrome the user needs to change the new setting, afterwards it works as before

Correct?

[Lineflyer]

My assumptions seem to be correct. Just tested 0.51 from master and it works with both Firefox and Chrome (with activated setting).

@capoaira
Stupid question:
Couldn't we get rid of the whole "third party cookie" problem if we use this option permanently and as a default without setting?

For two reasons:

• It difficult to explain Chrome users to apply this setting as we do not have a good communication channel
• Firefox might some day apply the same third party cookie blocking

[capoaira]

Yes, but for me the Window closed directly after loading and so I don't see if sending was successful or if I have to register first.
Because of that I have made the settings, so that all can use the old one.

I think in the long term, we should switch to a solution without third-party cookies. That needs changes in the server code. Than we can save the register data in Tampermonkay. So it isn't use cookies and the registration will not go list after some time.

[capoaira]

For my understanding:

• The script should work as before on Firefox and on "unaffected" Chrome
• With the problematic Chrome the user needs to change the new setting, afterwards it works as before

Correct?

Yes

[Lineflyer]

Will merge to release branch now, so that version 0.51 is live.

I will add a FAQ entry regarding the setting in Chrome in case of problems.