Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Marketo error message when editing email with Shield up #9665

Closed
frankfuu opened this issue May 7, 2020 · 11 comments
Closed

Marketo error message when editing email with Shield up #9665

frankfuu opened this issue May 7, 2020 · 11 comments
Labels
closed/fixed-by-component-update webcompat/lists Webcompat issues that seem to be because our lists of what to or not to block could be improved.

Comments

@frankfuu
Copy link

frankfuu commented May 7, 2020

Description

Error message "MKN: uninitialized() uninitialized()" shows up when trying to edit an email in Marketo

Steps to Reproduce

  1. Login to a Marketo instance
  2. Look for any email and click "edit"
  3. Make an edit
  4. Wait for auto save to kick in

Actual result:

image

Expected result:

Message not to appear.

Reproduces how often:

Every time.

Brave version (brave://version info)

Brave | 1.8.90 Chromium: 81.0.4044.129 (Official Build) (64-bit) |
Revision | 3d71af9f5704a40b85806f4d08925db24605ba25-refs/branch-heads/4044@{#979}
OS | Linux

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? Yes
  • Does the issue resolve itself when disabling Brave Rewards? N/A
  • Is the issue reproducible on the latest version of Chrome? N/A

I think the offending trackers could be one of the following

@fmarier fmarier added the webcompat/lists Webcompat issues that seem to be because our lists of what to or not to block could be improved. label May 7, 2020
@ryanbr
Copy link

ryanbr commented May 8, 2020

Which shield options is causing the issue @frankfuu ? (configure via the address bar)

@frankfuu
Copy link
Author

frankfuu commented May 9, 2020

Hi @ryanbr

I think it is the "Cross-site option trackers blocked" option. When I disable this option but keep Brave Shields up for this site it still functions properly so I'm guessing this could be the culprit?

image

@ryanbr
Copy link

ryanbr commented May 9, 2020

Ah great. can you copy/paste the trackers into this Github report?

ryanbr added a commit to easylist/easylist that referenced this issue May 10, 2020
@ryanbr
Copy link

ryanbr commented May 10, 2020

Give it 24-48hrs, this commit should help. Thanks for the report @frankfuu

easylist/easylist@1158dc9

I'll leave this ticket open to confirm

@frankfuu
Copy link
Author

Wow that was quick @ryanbr ! Thanks!

Do I need to be in Non-Release channels (e.g. Nightly / Beta) to check?

@ryanbr
Copy link

ryanbr commented May 10, 2020

Will be fixed in all channels :)

@ryanbr
Copy link

ryanbr commented May 15, 2020

How is it looking @frankfuu ? everything okay?

@frankfuu
Copy link
Author

Thanks @ryanbr ! That was lightning speed!

Confirmed fixed on Brave | 1.8.96 Chromium: 81.0.4044.138 (Official Build) (64-bit) , Revision 8c6c7ba89cc9453625af54f11fd83179e23450fa-refs/branch-heads/4044@{#999} on Linux

@rebron
Copy link
Collaborator

rebron commented Jun 12, 2020

@ryanbr ok to close this one?

@ryanbr
Copy link

ryanbr commented Jun 13, 2020

Yup closed.

@ryanbr ryanbr closed this as completed Jun 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed/fixed-by-component-update webcompat/lists Webcompat issues that seem to be because our lists of what to or not to block could be improved.
Projects
None yet
Development

No branches or pull requests

4 participants