Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

Μάθετε περισσότερα

Bookmark Navigation Changes in Last Update iOS

  • 1 απάντηση
  • 1 έχει αυτό το πρόβλημα
  • 4 προβολές
  • Τελευταία απάντηση από Kiki

more options

Each update iteration seems to make using bookmarks on my iPad require more navigation. Prior to the current update (early Feb 2022) when I clicked on the button to allow me to navigate to a bookmark I would select a folder and then a subfolder and then on a link in that folder. For subsequent navigation in the same session when clicking on the button to allow me to navigate, it opens to the subfolder previously selected.

Now when I click on the button I have to select the folder, then the subfolder, then the link. This seems to be a step backwards and is quite annoying.

Each update iteration seems to make using bookmarks on my iPad require more navigation. Prior to the current update (early Feb 2022) when I clicked on the button to allow me to navigate to a bookmark I would select a folder and then a subfolder and then on a link in that folder. For subsequent navigation in the same session when clicking on the button to allow me to navigate, it opens to the subfolder previously selected. Now when I click on the button I have to select the folder, then the subfolder, then the link. This seems to be a step backwards and is quite annoying.

Όλες οι απαντήσεις (1)

more options

Hi dgmsmiles, sorry about this,

I can confirm that our team is aware of this issue and currently looking into it. See https://github.com/mozilla-mobile/firefox-ios/issues/9856