I have a Lightning Component used in our community using the napili templates in our prod and sandbox environment with identical code that uses anchor tags to jump to headers within the component. Today, while testing something in our sandbox, I found that the anchor links now cause the whole page to reload before jumping to the correct header. Wondering if I had missed something, I checked out our prod environment only to find that it doesn't reload the page when jumping to the header. The only difference between the environments is Winter 17 in our sandbox.

I know that the documentation says to avoid using the hash (#) but it hasn't been an issue until this recent update.

Is there any indication of what changed in the newest release to cause this issue? Along with that, is there a workaround that works with this release to get this simple functionality back?

  • 2
    What is the container application that you are using the component in - e.g. one.app (Salesforce1/Lightning Experience), Visualforce, Canvas, your own custom .app? – Doug Chasman Sep 21 '16 at 10:08
  • It's in the community using napili templates. I'll update the question. – Matthew Green Sep 21 '16 at 13:59
  • any update on this @MatthewGreen – cartman Feb 3 '17 at 19:34
  • @cartman nope, I've just rewritten the component to no longer use the anchor tags anymore. Not ideal but better than a full reload of the page. – Matthew Green Feb 4 '17 at 20:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.