Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

[Add-ons][NoScript] The Homepage content is not displayed when the add-on is enabled #3844

Closed
Softvision-RemusDranca opened this issue Aug 20, 2020 · 3 comments
Labels
ARCHIVED CLOSED at time of archiving [QA]:Caught_by_exploratory Bugs found during exploratory testing [QA]:Major issue Label for QA to mark major issues logged

Comments

@Softvision-RemusDranca
Copy link

[Affected Versions]:

  • Firefox Reality v12 RC2 (195415f).

[Affected Platforms]:

  • Oculus Quest - Android 7.1.1
  • HTC Vive Focus - Android 7.1.2
  • Pico Neo2 - Android 8.1.0

[Prerequisites]:

  • The Firefox Reality browser is open.

[Steps to reproduce]:

  1. Open the Add-ons page from Library.
  2. Install the "NoScript Security Suite" add-on.
  3. Navigate to Homepage and observe the page.

[Expected results]:

  • The Homepage is correctly displayed.

[Actual results]:

  • No content is displayed on the Homepage.

[Notes]:

  • Attachments for the issue:
    • Screen Recording: link.
@Softvision-RemusDranca Softvision-RemusDranca added [QA]:Major issue Label for QA to mark major issues logged [QA]:Caught_by_exploratory Bugs found during exploratory testing labels Aug 20, 2020
@keianhzo
Copy link
Contributor

That's how that add-on works. It would be the same if you install it on Desktop and have webxr.today as the default page. We can't add exceptions to the addon at install time so there is not much that we can do about it. The user would need to allow the site in the add-on settings.

@keianhzo keianhzo reopened this Aug 21, 2020
@Softvision-RemusDranca
Copy link
Author

@keianhzo I understand your point of view. What I took in consideration is also the fact that a user might not be sure how to add it to exceptions and that is not certain which add-on could cause this in the case of multiple add-ons installed. This consideration can be balanced on how much a user uses the content from Homepage and also if we consider that we want to have our content always displayed.

On a second matter, after further investigation, it seems that the add-on also blocks other content that we provide, if not added to exceptions of course. For example "Hello WebXR", "Hubs". Here is a video.

@Softvision-RemusDranca
Copy link
Author

@keianhzo @emstanley , could this issue also be a case in where we inform users that don't know the add-on's functionality blocks some content until the website is manually added to exceptions or disabled/removed?
We discussed in our meeting about adding issue #3795 for the "Dark Reader" add-on into a "known issues" base, when if a user might encounter it should know what the next steps are in resolving it.

@cknowles-admin cknowles-admin added the ARCHIVED CLOSED at time of archiving label Jul 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ARCHIVED CLOSED at time of archiving [QA]:Caught_by_exploratory Bugs found during exploratory testing [QA]:Major issue Label for QA to mark major issues logged
Projects
None yet
Development

No branches or pull requests

3 participants