Share via

MS FORMS - link opening on wrong section

Anonymous
2022-11-06T22:18:08+00:00

Hello,

I am encountering an odd issue in MS forms.

I have a few different forms, most of which are working fine. However one of them is opening to the wrong section (not opening from the start page) whenever the link is clicked. This issue is occurring in chrome, however seems to work fine in edge. And no other forms are affected.

While I can get it to work in edge, I would like to rectify this issue as our organisation is hoping to share these forms publicly and it would look more professional if they work across multiple browsers.

Microsoft 365 and Office | Install, redeem, activate | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2022-11-07T02:06:55+00:00

Dear TGJAG,

Good day! Thank you for posting to Microsoft Community. We are happy to help you. 

Per the descriptions shared, I would like to summarize your concern i.e., when you open a specific form it opens the section in the Form instead of opening the start of the page and the problem happens only in the Google Chrome.

If my understanding is correct, as the problem doesn't happen in the Microsoft Edge browser, I believe the problem is not related to the Form and I would like to suggest you open the Incognito browser in the Google Chrome and access the Form to see the outcome.

If the problem doesn't persist, it seems the problem is caused due to the Google Chrome browser cache, so suggest you clear it to resolve the problem.

We look forward to your response. Thanks for your cooperation.

Sincerely,

Mia | Microsoft Community Moderator

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2022-11-07T02:18:23+00:00

    Thank you so much for your reply Mia

    You are correct - it was the Chrome browser cache!

    Was this answer helpful?

    0 comments No comments