Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

webmail links dont work

more options

I have a frequent issue where my email causes odd behavior. I open an email, it looks ok, but I can not scroll with the scroll wheel and if I click something in the email, it exits and clicks on what ever was it the cursor like the email was not open. as in opening another email. it does not matter which button i use. Oddly I can use the mouse button on the email scroll bar to scroll.

After this happens, I have this behavior continue, it happens frequently, and not always on the first email. This only happens on Outlook.com, that I have seen.

Workaround: When this happens, I have to click "Refresh" sometimes I have to do this per message.


From Microsoft: My name is Franco and I am here to help. I have encountered something similar with 2 other customers. Oddly enough, all instances involved Firefox. I'm not sure what Mozilla had to say but let me ask you to do the same thing I asked of the 2 other people I worked with.

Please try opening your account in a different browser. It's best if you do it when the page begins to act up in Firefox. You can then open the same exact message on the other browser to see if the same thing happens on another program. Also, would you be able to perform the same test on a totally different device?

I look forward to hearing from you.

Franco M Outlook.com Support

I have a frequent issue where my email causes odd behavior. I open an email, it looks ok, but I can not scroll with the scroll wheel and if I click something in the email, it exits and clicks on what ever was it the cursor like the email was not open. as in opening another email. it does not matter which button i use. Oddly I can use the mouse button on the email scroll bar to scroll. After this happens, I have this behavior continue, it happens frequently, and not always on the first email. This only happens on Outlook.com, that I have seen. Workaround: When this happens, I have to click "Refresh" sometimes I have to do this per message. -------------------------------------------- From Microsoft: My name is Franco and I am here to help. I have encountered something similar with 2 other customers. Oddly enough, all instances involved Firefox. I'm not sure what Mozilla had to say but let me ask you to do the same thing I asked of the 2 other people I worked with. Please try opening your account in a different browser. It's best if you do it when the page begins to act up in Firefox. You can then open the same exact message on the other browser to see if the same thing happens on another program. Also, would you be able to perform the same test on a totally different device? I look forward to hearing from you. Franco M Outlook.com Support

Zvolené řešení

Hi jefftoo, yes, it's a bug. A team of developers worked on this over the weekend and developed a fix that is in testing this week in the Nightly release. Firefox 58 probably won't get that update for 1-3 weeks...

These are all the workarounds I'm aware of (other than using zoom in the message to temporarily fix the mouse behavior in that one message, e.g., Ctrl+ or Ctrl-):

(1) Use the Reading pane

If you have a wide display, you could try using the Reading pane on the right side of the Inbox.


(2) Switch to the Outlook beta layout

There is a "Try the beta" switch above the Inbox. You'll be able to switch back equally easily if you don't like it.


(3) Revert to the older layout engine for the site

(A) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(B) In the search box above the list, type or paste stylo and pause while the list is filtered

(C) Double-click the layout.css.stylo-blocklist.enabled preference to switch the value from false to true

(D) Double-click the layout.css.stylo-blocklist.blocked_domains preference and set the value to live.com and click OK. (In the unlikely event that you already had one or more sites listed add ,live.com to the list.)

Then exit/quit Firefox and start it up again to make the change effective.

Do any of those suit your needs?

Přečíst dotaz v kontextu 👍 1

Všechny odpovědi (3)

more options

Zvolené řešení

Hi jefftoo, yes, it's a bug. A team of developers worked on this over the weekend and developed a fix that is in testing this week in the Nightly release. Firefox 58 probably won't get that update for 1-3 weeks...

These are all the workarounds I'm aware of (other than using zoom in the message to temporarily fix the mouse behavior in that one message, e.g., Ctrl+ or Ctrl-):

(1) Use the Reading pane

If you have a wide display, you could try using the Reading pane on the right side of the Inbox.


(2) Switch to the Outlook beta layout

There is a "Try the beta" switch above the Inbox. You'll be able to switch back equally easily if you don't like it.


(3) Revert to the older layout engine for the site

(A) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(B) In the search box above the list, type or paste stylo and pause while the list is filtered

(C) Double-click the layout.css.stylo-blocklist.enabled preference to switch the value from false to true

(D) Double-click the layout.css.stylo-blocklist.blocked_domains preference and set the value to live.com and click OK. (In the unlikely event that you already had one or more sites listed add ,live.com to the list.)

Then exit/quit Firefox and start it up again to make the change effective.

Do any of those suit your needs?

more options

Having same issue here... click on a link in an email and it takes you back tot he main page and opens whatever email was under the curser when you clicked it. Only happened since i updated to quantum.

more options

Hi leovon1, try workaround #3 in my earlier reply.