1706240 - spam

Status: RESOLVED INVALID

(Invalid Bugs :: General, defect, P5)

Description

[samsol nol]

Thank you for helping make Firefox better. If you are reporting a defect, please complete the following:

What were you doing?

Please tell us what site you were on, and what steps led to the error you are reporting

1. First step
2. Second step
3. …

What happened?

What, if any, error messages did you see? Did the browser crash? Screenshots or screen recordings can be attached to this report and are helpful in isolating and replicating the bug.

What should have happened?

Was was the expected result? ("Not crashing" may be a valid answer.)

Anything else we should know?

Do you have extensions installed? You can also go to about:support in another window or tab and attach the report it generates to this bug.

Comment 1

[samsol nol]

kamu menulis apaan di dalam bug ini saya hanya ingin membagikan link
<a href="https://pkv7799.makewebeasy.co">situs judi pkv games</a>

Comment 2

[samsol nol]

kamu menulis apaan di dalam bug ini saya hanya ingin membagikan link
https://pkv7799.makewebeasy.co
https://linktr.ee/pkvgamestop
https://situsslot.makewebeasy.co/
https://agenjudi.makewebeasy.co/
https://pkvgamestop.makewebeasy.co/
https://judipkv.makewebeasy.co/
https://mainbola.makewebeasy.co/
https://spark.adobe.com/page/VyJQOgnb9w3wh/
https://support.themecatcher.net/forums/users/samsolnol
https://dashburst.com/samsolnol
https://pixelhub.me/samsolnol
https://cults3d.com/en/users/samsolnol
https://www.bizcommunity.com/Profile/samsolnol

Comment 3

[samsol nol]

Description:
Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s).
Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change.

How do we test this?
If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc.

When will this ship?
Tracking bug/issue:
Design documents (e.g. Product Requirements Document, UI spec):
Engineering lead:
Product manager:

The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:
https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:

Describe any areas of concern to which you want the accessibility team to give special attention:

Comment 4

[samsol nol]

Release Note Request (optional, but appreciated)
[Why is this notable]:
[Affects Firefox for Android]:
[Suggested wording]:
[Links (documentation, blog post, etc)]: