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

Optimize settings form displays "use snippet instructions" for a moment and hides it #3720

Closed
eugene-manuilov opened this issue Jul 15, 2021 · 4 comments
Labels
Good First Issue Good first issue for new engineers Module: Optimize Google Optimize module related issues P2 Low priority Rollover Issues which role over to the next sprint Type: Bug Something isn't working
Milestone

Comments

@eugene-manuilov
Copy link
Collaborator

eugene-manuilov commented Jul 15, 2021

Bug Description

When I open Optimize settings form, I see the form shows me use snippet instructions for a moment and then hides it.

Screencast.2021-07-15.20.22.15.mp4

Looks like it happens because Analytics settings haven't been resolved yet and the settings form from the Optimize module thinks that the useSnippet setting is disabled.

Steps to reproduce

  1. Set up Optimize
  2. Go to Settings
  3. Wait a few seconds, then click Edit on Optimize
  4. See the AMP experiment JSON setting input momentarily before disappearing (this can be exaggerated by simulating Slow 3G network speed)

Screenshots

Screenshot from 2021-07-15 20-22-59


Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

  • The Optimize AMP experiment JSON setting input field should not display if the useSnippet setting for Analytics is disabled, or the AMP mode is false (this is the current logic)
    • This should be more strictly checked to avoid false positives when settings are not resolved yet

Implementation Brief

Test Coverage

  • N/A

Visual Regression Changes

  • N/A

QA Brief

  • use snippet instructions in the optimize settings form shoul no longer flash for a few ms.

Changelog entry

  • Update Optimize module settings to avoid the flash of use snippet instructions when Analytics settings are being resolved.
@eugene-manuilov eugene-manuilov added Type: Bug Something isn't working P2 Low priority Module: Optimize Google Optimize module related issues labels Jul 15, 2021
@aaemnnosttv
Copy link
Collaborator

@eugene-manuilov it looks like this is no longer an issue. Can you confirm? If so, please close this issue 👍

@eugene-manuilov
Copy link
Collaborator Author

@aaemnnosttv I still see it on my end.

@aaemnnosttv aaemnnosttv removed their assignment Sep 6, 2021
@eugene-manuilov eugene-manuilov self-assigned this Sep 7, 2021
@eugene-manuilov eugene-manuilov added the Good First Issue Good first issue for new engineers label Sep 7, 2021
@eugene-manuilov eugene-manuilov removed their assignment Sep 7, 2021
@tofumatt tofumatt self-assigned this Sep 7, 2021
@tofumatt tofumatt added this to the Sprint 57 milestone Sep 7, 2021
@tofumatt
Copy link
Collaborator

tofumatt commented Sep 7, 2021

IB ✅

@tofumatt tofumatt removed their assignment Sep 7, 2021
@tofumatt tofumatt modified the milestones: Sprint 57, Sprint 58 Sep 7, 2021
@kuasha420 kuasha420 self-assigned this Sep 21, 2021
@kuasha420 kuasha420 removed their assignment Sep 21, 2021
@fhollis fhollis added the Rollover Issues which role over to the next sprint label Sep 27, 2021
@fhollis fhollis modified the milestones: Sprint 58, Sprint 59 Sep 27, 2021
@wpdarren wpdarren self-assigned this Sep 27, 2021
@wpdarren
Copy link
Collaborator

QA Update: ✅

I was able to recreate the initial issue. Then when on develop branch and reconnected Optimize, and edited the settings the issue is fixed. Use snippet instructions in the optimize settings no longer flash for a few ms.

@wpdarren wpdarren removed their assignment Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Good First Issue Good first issue for new engineers Module: Optimize Google Optimize module related issues P2 Low priority Rollover Issues which role over to the next sprint Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

7 participants