Source evidence

Detects end too soon

Sticky Element · support · 2014-12-18T07:23:00+00:00

Sticky Element plugin evidence original source source API

mixedsentiment

mediumseverity

0.72relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

2 / 24 rows with source links

8.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

22 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

Simon Barnett resolved

When scrolling on posts and archives, the sticky element detects the end (element which pushes up) too soon. It works fine on pages. Example using: Genesis / Dynamik Website Builder Standard version of Sticky Element (not my modified version from previous post) No other plugins Noticed this behaviour on other sites too. https://wordpress.org/plugins/sticky-element/ To partially answer my own question: I had set up a large, extra <footer> to test pushing the sticky element up. I used footer as the end selector in the plugin settings. I think seeing as the site already had a <footer> lower down the post and archive pages it confused the jQuery listener. I changed the end selector to the CSS class of my extra footer: .bigfoot and that fixed the issue. This still doesn’t explain why it worked on pages but not posts. For flexibility I’d prefer to know the answer to that so I’ll leave this topic open in case there’s a quick technical explanation. An example of flexibility would be a site where I have a special extra footer on some pages but not others. A way to cheat this would be to include an invisible, height: 0 extra footer on all the pages that don’t require an extra footer. Then the plugin will detect something. My only guess is the selector is different for posts than pages.

Commercial Context

Opportunity

onsite conversion and engagement operations

Sticky conversion widget assurance for turning onsite engagement widgets into measurable leads, trust, and conversions

Buyer: marketing teams, agencies, publishers, and ecommerce operators

Wedge: audit sticky display rules, lead capture, trust signals, and campaign attribution

Investigate Pain card complete market

Analysis

heuristic-v1

Summary: Detects end too soon: users show bugs, missing feature pain that may indicate a product gap.

Evidence quote: It works fine on pages.

Affected feature: bugs

bugs missing feature easy reliable

Plugin

API

Sticky Element

200 active installs · 17.4K downloads · rating 74.0

fixed scroll sticky

Comments

2 shown

Simon Barnett 2014-12-18T11:12:00+00:00

To partially answer my own question: I had set up a large, extra <footer> to test pushing the sticky element up. I used footer as the end selector in the plugin settings. I think seeing as the site already had a <footer> lower down the post and archive pages it confused the jQuery listener. I changed the end selector to the CSS class of my extra footer: .bigfoot and that fixed the issue. This still doesn’t explain why it worked on pages but not posts. For flexibility I’d prefer to know the answer to that so I’ll leave this topic open in case there’s a quick technical explanation. An example of flexibility would be a site where I have a special extra footer on some pages but not others. A way to cheat this would be to include an invisible, height: 0 extra footer on all the pages that don’t require an extra footer. Then the plugin will detect something.

Youdaman 2015-07-18T11:01:00+00:00

My only guess is the selector is different for posts than pages.