Getoonde gelabelde vragen: Alle vragen tonen

Hotkeys for custom context-menu items

I've written an extension that adds a custom entry to my right-click menu (browser.contextMenus.create), but can't seem to find a way to make this function fire via hotke… (meer info)

I've written an extension that adds a custom entry to my right-click menu (browser.contextMenus.create), but can't seem to find a way to make this function fire via hotkey (after right-clicking). Would this be possible?

Gevraagd door eipvwrqxjlugolezmg, 6 dagen geleden

Bell Canada video taking almost all my memory. Not sure if it's the website or firefox. Did memory measurement.

Strange problem. My provider, Bell Canada, has an option via their website for me to view anything from live Bell TV or even my PVR on any device with a browser (in my ca… (meer info)

Strange problem. My provider, Bell Canada, has an option via their website for me to view anything from live Bell TV or even my PVR on any device with a browser (in my case latest Firefox on win10). The problem is it is taking up most of my ram, and as I'm sure many will attest to, when Win10 has less than a couple of GB of ram, it just grinds to a halt (30-40 seconds to open a tiny 10kB spreadsheet, etc.).

I did a memory measurement from the about: thing. Perhaps one of you wizards can tell me if it's a firefox issue or a problem with the Bell website/scripts/whatever? I just cannot believe that it takes 8 GB to watch a video stream. That's more than an entire DVD movie - with all the alternate-language soundtracks and special features!

10,369.05 MB (100.0%) -- explicit ├───8,475.00 MB (81.73%) -- window-objects │ ├──8,473.59 MB (81.72%) -- top(https://tv.bell.ca/watch/recording- (deleted info) │ │ ├──8,257.39 MB (79.63%) -- active │ │ │ ├──8,254.29 MB (79.61%) -- window(https://tv.bell.ca/watch/recording (deleted info) │ │ │ │ ├──7,967.99 MB (76.84%) -- js-realm(https://tv.bell.ca/guide) │ │ │ │ │ ├──7,932.14 MB (76.50%) -- classes │ │ │ │ │ │ ├──6,769.33 MB (65.28%) -- class(ArrayBuffer)/objects │ │ │ │ │ │ │ ├──6,767.27 MB (65.26%) ── malloc-heap/elements/normal │ │ │ │ │ │ │ └──────2.05 MB (00.02%) ── gc-heap

  (deleted info, small memory elements)

├───1,703.55 MB (16.43%) ── heap-unclassified

Ouch. I mean, ouch. Good to find out if there's some way to fix this. Thanks ahead of time! Avner

Gevraagd door Avner, 3 dagen geleden

NEW UI - PC =/= TOUCHSCREEN, MOZILLA WAKE UP

The Firefox Community here has tried to be very helpful with all the users who hate the changes in Version 89/90, but we need Mozilla/Firefox to hear us. CSS work-arounds… (meer info)

The Firefox Community here has tried to be very helpful with all the users who hate the changes in Version 89/90, but we need Mozilla/Firefox to hear us.

CSS work-arounds are fine for the IT-literate, which I am not. They are also only temporary. We have no indication that FF is even paying attention to our complaints.

They need to understand that some users have a keyboard and mouse attached to a PC, not a touchscreen like on a pad or phone. It looks like FF wants to cater to touchscreens. This DOES NOT WORK for PC users.

I suggest one UI for touchscreens and a different one for PCs. IIRC, there is a FF version for Windows AND a different one for Apple; why not do the same?

Nobody seems to have any response other than "use this CSS fix." I've also been directed to "clean up the help platform myself" - huh?

Can we please get SOME kind of response from the platform itself? Or are they just trying to get rid of all users without touchscreens?

Gevraagd door fidservant, 4 dagen geleden

Laatst beantwoord door fidservant, 2 dagen geleden