I am running an experiment in Google Analytics and I want to stop it. I am reading the documentation at https://support.google.com/analytics/answer/2366607?hl=en and it says:
To stop a running experiment:
In the experiment list, click the name of the experiment that you want to stop.
In the menu bar, click STOP EXPERIMENT, then click the confirmation.
Where is the "menu bar" that they mention, which is where I am supposed to find this "STOP EXPERIMENT" link. Look at what I get when I go to my running experiment:
Edit:
It is right there. It says "Stop Experiment" in the navigation area on top with the gray background. I was expecting to find something more prominent like a button that is easy to see/find. This would probably be a usability feedback for Google, that they should make that button more prominent. I am used to running experiments in Optimizely and they have the play or pause button in a much more prominent way. I like the graphical user interface of Optimizely better than Google Analytics's GUI.
I found it. It says "Stop Experiment" in the navigation bar with the gray background.
Related
I've seen that in earlier versions of AEM, when we schedule a page to get activated at a later time, a small calendar icon is showing up under the status column. When we hover over this icon, it displays the scheduled date and time.
But, I can't see that scheduled activation calendar icon anymore. I can only see the workflow icon under the status column.
Is there a way how I can display the scheduled activation status icon in AEM 6.5?
Many thanks in advance for all your help.
This should still be visible by default in AEM 6.5 so you may not need any custom implementation. If it isn't working, maybe there's a bug or there's an existing customization that's preventing those icons from working.
In the list view
In the column that displays the publication status, there's a faint calendar icon. It's quite low-contrast though. Hovering over it will reveal the scheduled publication date.
In the card view
You should be able to see the time of scheduled activation in the page preview on the right hand side.
How you could change or add icons
If you still want to add an icon, you should be able to achieve this via overlaying parts of the sites console. You'd have to find the right scripts under /libs and create an overlay under /apps
This is also where you'd look if any icons available OOTB are missing.
More on the subject:
Using the Sling Resource Merger
Customizing the consoles
I use embedded google slides for my website. Earlier, on android, tapping on the slides used to progress the slides. However, I'm noticing that in version 92.xxxxx, it is no longer happening. The user needs to click on the > button on the bottom navigation bar to progress the slides. However, the problem with that is the > button is too small and the user needs to be very careful while clicking it. For our use case, tapping on the slides was the best way to progress with the slides.
The only solution I can think of is to progress the slides at a specific interval. However, it is hard to figure out an interval that suits all the users. Is there any other possible solution? Like can we create two external navigation buttons and send the signal to the embedded slide?
The website of PageSpeed Insight is the only place, where i get CLS issue in both of field and lab data.
Any other Lighthouse instance (by WPT, as API or by DevTools) displays CLS issue only in field data, not in the lab.
How can i diagnose correctly, which elements are causing CLS? Example.
PS: My question has the following cause: analyzing other websites i usually have under devtools → performance red diamonds layout shift, which, if clicked, display in tab Summary some data about this layout shift. Like on the screenshot:
But on the example site i get CLS diagnosted, but not displayed.
The synthetic (lab) tests only load the page (they do not interact with it), whereas field data is until page unload.
Immediately I can see one Layout shift is when you open either of the drop down menus, your scroll bars disappear (due to adding the class .overlayed) and the whole page shifts around. Synthetic tests do not open the menu so will never capture it, however this shouldn't actually contribute to CLS as it requires interaction to open (just something to fix).
The other thing I noticed is the bottom right corner icons cause a layout shift when you scroll and they collapse / open (the floating icons). This is likely to be the cause of CLS as it isn't via direct interaction. Scrolling does not count as user interaction when it comes to CLS.
My guess is that this is the one that gets found by synthetic tests sometimes and not others.
Finding Layout Shifts
In order to find layout shifts you can open developer tools, go to rendering panel (you may need to open it with "more tools") and click "Layout Shift Regions" so it is selected.
Now use the site and you will get a blue box around anything that shifts.
Or you could use performance traces
The other way is to run a performance trace in the performance tab and then just use the site. Once you are done complete the trace and it will tell you if a layout shift occurred and what item caused it.
Tracking them in the field
In order to capture layout shifts in the field yourself you should use something like Google Web Vitals library along with click / mouse position tracking etc and pipe it to your own backend or Google Analytics for analysis.
This lets you find issues with the page a lot more quickly and easily using Real User Metrics (RUM) data in real-time.
I'm writing a Firefox (web)extension. I have a browser_action in my manifest.json, with a default_popup. I want my extension to be accessible by all users, including those with vision impairment.
So I'd like to, as I change and develop things, test what it's like to (for example) interact with this feature, using only the keyboard. How do I do this? How do I focus and thus "click" the toolbar button, without a mouse?
Ideally, without actually running special screen reader software every time.
So I'd like to, as I change and develop things, test what it's like to
(for example) interact with this feature, using only the keyboard. How
do I do this? How do I focus and thus "click" the toolbar button,
without a mouse?
You can use commands to set a keyboard shortcut.
_execute_browser_action: works like a click on the extension's browser action
You may also add commands.update() (Firefox 60+) API to let users change that keyboard shortcut.
Thanks for considering accessibility. Just to clarify, because I don't think you meant this, but you can do keyboard testing without a screen reader. Just don't use your mouse :-) Seriously.
In my current firefox, I have an address bar, the search field, then a bunch of plugins on a toolbar.
On a PC (should be similar for a Mac, but Cmd instead of Ctrl):
I can move my keyboard focus to the address bar with alt+d or ctrl+L (cmd+L)
I can move my keyboard focus to the search field with ctrl+k (cmd+k)
Interestingly enough, I could not get my focus on the toolbar. I could have sworn I could tab from the address field, to the search field, to the toolbar, but it's not working now.
If you can get your focus there, then you should be able to use the left/right arrows to move between tools and then space/enter to select the tool.
If you want to play with a screen reader, NVDA is free.
Fiddler is a great tool.
However something that drives me crazy is the fact that they have several options on the toolbar, but the most important one, the 'Capture Traffic' toggle is only available from the menu.
I know that you can press F12. However when I am in the middle of development, I can't remember if I turned it back on, or its still off. There is nothing to show you if the 'Capture Traffic' toggle is on or off, without looking at the menu.
I have tried looking online, and here at SO for anything on how to modify the toolbar to add this feature, but I did not find anything.
This is a minor problem, but if someone knows how to add this to the Fiddler toolbar, that would be great.
I'm not sure which version of Fiddler you are using, but in v4.4.5.1 there is a useful button in the status bar:
You can click on it to toggle capturing on or off (and if it is not visible then Fiddler is not capturing:)).