Opened 10 years ago
Closed 4 years ago
#39191 closed defect (bug) (worksforme)
Twenty Seventeen: Warning in Firefox console for scroll-linked positioning effect.
| Reported by: | Shelob9 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Bundled Theme | Version: | 4.7 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
When I use TwentySeventeen with Firefox (50.0.2 for Ubuntu) I get this warning on the front page in my console:
This site appears to use a scroll-linked positioning effect. This may not work well with asynchronous panning; see https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects for further details and to join the discussion on related tools and features!
Does not happen with TwentySixteen or in Chromium.
#38850 is related as it is about same warning, but is happening in the editor.
Change History (5)
#1
@
10 years ago
- Keywords needs-patch added
- Milestone Awaiting Review → Future Release
- Summary TwentySeventeen Warning in Firefox console. → Twenty Seventeen: Warning in Firefox console for scroll-linked positioning effect.
This ticket was mentioned in Slack in #core-customize by sirbrillig. View the logs.
10 years ago
#3
@
6 years ago
- Keywords needs-patch removed
- Milestone Future Release
- Resolution → worksforme
- Status new → closed
I just tested this issue in FireFox 73.0.1 and no longer see the error. I am going to close this for now, but it can be reopened if needed.
#4
@
6 years ago
- Resolution worksforme
- Status closed → reopened
Hi,
this is still an issue.
If you visit http://2017.wordpress.net in Firefox and start to scroll you still get the warning in the console.
The warning is a result because of how the sticky-menu is implemented in Twentyseventeen.
Firefox suggests the »sticky«-css should be used.
So please change the implementation of the menu in upcoming theme-updates to meet Firefox’s best practice suggestion.
Thanks.
Best.
Christoph.
#5
@
4 years ago
- Resolution → worksforme
- Status reopened → closed
I just tested this again, and I'm unable to reproduce using Firefox 102.0.1 on MacOS. Additionally, the link included in the ticket description from the original console warning is now a 404, so it seems this has fixed itself.
If this is not the case, please feel free to reopen and include updated information.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
Thanks for the report @Shelob9! This is only a warning, so I'm not too worried about it. But we might be able to adjust the JavaScript to avoid the warning and be more performant. It's worth further investigation. Any patch will need to be mindful of the theme's current browser support and not breaking any existing sites.