All Products Community Forum

Hi all,

About a week ago a website began to be rendered incorrectly on the nightly build for Android.

Where is the best place to report such an issue for Nightly releases?

I use Firefox Nightly, currently 132.0a1, installed from Google Play. I've tried to disable extensions, same outcome.

The site renders correctly on Firefox Beta, 130.0b9.

The affected site. https://www.yr.no/en/details/graph/2-2618425/Denmark/Capital%20Region/Copenhagen/Copenhagen

Hello, I have Translated Kirati (Limbu, English, Nepali) Dictionary Spoken by approx 900,000 in (Nepal,India,Myanmar) Google Sheet in .PDF Format. Who do I have to approach in order to include my Mother Language in Google Translation and other Operating Systems? Your kind help in this matter would be highly appreciated. Thanking you. Kind regards.

I'm trying to pair my Pocket account on my Kobo Clara. I've tried pairing using both my phone and Desktop using the Firefox browser on the most recent versions. When I press the authorize button I receive an error saying "There was a problem trying to connect this app to Pocket. Please try again." The Desktop site is a little more descriptive saying "Can't log in to Pocket We're currently experiencing intermittent issues logging in to Pocket accounts. We're working closely with Pocket to resolve the situation, and apologize for any inconvenience. Please try logging in later." I'm not sure if this a Pocket error or a Kobo error. But any help would be appreciated, thank you!

September 14th 2024

5:56pm

Guys because of the way the INTERNET is set up, none of our complaints are getting through to folks in other states i.e the Federal Government/White House. Y'all are going to realize how much these internet companies and phone companies control. I'm trying to contact the White House and another agency. Realize what and who controls wifi and phone internet. I've submitted alot of things and need help. No response needed, but if you know someone, have them look into security breaches with federal agencies. Especially in North Carolina. I said with the White House because I can't tag anyone. Our complaints go to a STATE BERAEU AND NOT THE FEDERAL BERAEU is all I'm going to say! I can't even download another browser through the play store! I need help. They control everything including your app. Contact the president about these agency breaches. People need help. This is serious. Get white house involved. Please help us. I'm Jakime Lamar Ellison. Too many are against. Please be one to help.

Improving documentation organization can greatly enhance its usability and readability. Here are some tips to help you get started:

1. 1. 1. 1. **Structure and Hierarchy**

- **Table of Contents**: Start with a clear table of contents (TOC) that outlines the main sections and subsections of your documentation. - **Headings and Subheadings**: Use consistent and descriptive headings (H1, H2, H3, etc.) to break down content into manageable sections.

1. 1. 1. 2. **Consistent Formatting**

- **Markdown**: Utilize Markdown for consistent formatting. For example:

 ```markdown
 # Main Heading
 ## Subheading
 - Bullet point
 1. Numbered list
 ```

- **Code Blocks**: Use code blocks for any code snippets or commands:

 ```python
 def example_function():
     print("Hello, World!")
 ```

1. 1. 1. 3. **Clear and Concise Language**

- **Simplicity**: Write in clear, concise language. Avoid jargon unless necessary, and provide definitions for any technical terms. - **Active Voice**: Use active voice to make instructions more direct and easier to follow.

1. 1. 1. 4. **Visual Aids**

- **Diagrams and Screenshots**: Include diagrams, flowcharts, and screenshots to illustrate complex concepts or steps. - **Tables**: Use tables to organize data and comparisons.

1. 1. 1. 5. **Navigation and Links**

- **Internal Links**: Use internal links to connect related sections within your documentation. - **External Links**: Provide links to external resources for further reading or tools.

1. 1. 1. 6. **Search Functionality**

- **Search Bar**: If your documentation is hosted online, ensure it has a search bar to help users find information quickly.

1. 1. 1. 7. **Version Control**

- **Changelog**: Maintain a changelog to document updates and changes to your documentation. - **Version Numbers**: Clearly indicate the version of the documentation and the corresponding version of the software or project.

1. 1. 1. 8. **Feedback and Iteration**

- **User Feedback**: Encourage users to provide feedback on the documentation. Use this feedback to make continuous improvements. - **Regular Updates**: Regularly review and update the documentation to keep it current and accurate.

1. 1. 1. Example Structure

Here's a simple example of how you might structure your documentation:

```markdown

1. Project Title

1. 1. Table of Contents

1. [Introduction](#introduction) 2. [Installation](#installation) 3. [Usage](#usage) 4. [API Reference](#api-reference) 5. [FAQ](#faq) 6. [Changelog](#changelog)

1. 1. Introduction

Brief overview of the project.

1. 1. Installation

Step-by-step instructions on how to install the project.

1. 1. Usage

Examples and explanations of how to use the project.

1. 1. API Reference

Detailed information about the API endpoints or functions.

1. 1. FAQ

Common questions and answers.

1. 1. Changelog

List of changes and updates. ```

By following these tips, you can create well-organized, user-friendly documentation that is easy to navigate and understand. If you have any specific questions or need further assistance, feel free to ask!