Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

Firefox's not referring to 'next pages'

  • 1 yanıt
  • 1 kişi bu sorunu yaşıyor
  • 1 gösterim
  • Son yanıtı yazan: Jonathan Watt

foxesden1
foxesden1
more options

Yesterday I needed to print out a 2 page set of labels sent to me by Ebay to return something. My printer would only print the 2nd page, over, and over again. I never was able to print the first page of the labels with the address on it in order to return the item.

I suddenly twigged that Firefox has something that stops it referring to another page, and went to another browser in order to get my printing job done.

However I'd rather use Firefox for all things, so how do I overcome Firefox not allowing me to load and print the second page of labels/ refer to another page when I give it permission to? How do I give FF permission to refer to other pages in certain circumstances?

Yesterday I needed to print out a 2 page set of labels sent to me by Ebay to return something. My printer would only print the 2nd page, over, and over again. I never was able to print the first page of the labels with the address on it in order to return the item. I suddenly twigged that Firefox has something that stops it referring to another page, and went to another browser in order to get my printing job done. However I'd rather use Firefox for all things, so how do I overcome Firefox not allowing me to load and print the second page of labels/ refer to another page when I give it permission to? How do I give FF permission to refer to other pages in certain circumstances?

Tüm Yanıtlar (1)

Jonathan Watt
Jonathan Watt
more options

That's this issue I believe: https://bugzilla.mozilla.org/show_bug.cgi?id=1669071

Hopefully we'll get that fixed in the next month or two.