Closed Bug 859629 Opened 7 years ago Closed Last year

Facebook, multiple sites, not accepting click target fluff

Categories

(Core :: Layout, defect, P2)

x86_64
Windows 8.1
defect

Tracking

()

RESOLVED WONTFIX

People

(Reporter: kjozwiak, Unassigned)

References

Details

(Whiteboard: [metro] p=0 [platform-rel-Facebook])

When attempting to tap near any links on the Facebook login screen, the "ui.mouse.radius" feature isn't working correctly and will not select the link. If a user misses the link when tapping, it will not select the link like it would  at Wikipedia.

Think this issue is worth investigating as Facebook is one of the top websites that is visited by touch devices.

Steps to reproduce the issue:

1) Open Firefox Metro
2) Go to facebook.com and ensure that you are currently logged off
3) Tap near the bottom or top of the "Login" button (notice it will not select the link)
4) Go into "about:config" and change "ui.mouse.radius.topmm" and "ui.mouse.radius.bottommm" to 20
5) Go back into the Facebook login screen and attempt Step # 3 (same results)
6) Go into en.wikipedia.org/wiki/Mozilla and try tapping near the top or bottom of several links, you will notice that the link will be selected

Current Behavior:

- Tapping and missing a link in Facebook will not select it as other sites like Wikipedia would

Expected Behavior:

- Should work the same as it would on other websites. If a user misses the link but is in the correct radius, it should select the link.
consideration for Iteration #6
Flags: needinfo?(mmucci)
/me thinks a good title for this could have been found if you used Facebook's poke feature as the fluff target!
For consideration in upcoming iterations.
Blocks: metrov1defect&change
No longer blocks: metrov1it6
Flags: needinfo?(mmucci)
QA Contact: jbecerra
Whiteboard: feature=defect c=Content_features u=metro_firefox_user p=0
Priority: -- → P3
Whiteboard: feature=defect c=Content_features u=metro_firefox_user p=0 → [shovel-ready] feature=defect c=Content_features u=metro_firefox_user p=0
Found several other websites that don't accept click target fluffing. Seems this issue will probably affect a good amount of websites:

- drupal.org
- polygon.com
- metafilter.com

I am sure there's a lot more out there. This makes it really difficult to navigate through some websites as you have to directly select the links. Sometimes with the fluffing enabled, you will see the link "highlight and change color" but you will not be redirected (metafilter.com is a good example)
Bug 788073 comment 12 mentions that this can happen on pages where the top-level <html> element has a click event listener.
Depends on: 901117
Went through this issue again as it looked like there was some work done relating to fluffing (Bug 901117) but I'm still getting the same issues. Tried using same websites as per comment #5 but fluffing wasn't working properly (also tried the login page on Facebook)

If you go to wikipedia.org, you'll notice that fluffing is working correctly compared to the websites mentioned in comment #5 (including the Facebook login page).

Was using the following build:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-08-31-03-02-24-mozilla-central/
No longer blocks: metrov2defect&change
Summary: Defect - Facebook not accepting click target fluff → Facebook not accepting click target fluff
Whiteboard: [shovel-ready] feature=defect c=Content_features u=metro_firefox_user p=0 → [defect] p=0
Summary: Facebook not accepting click target fluff → Facebook, multiple sites, not accepting click target fluff
Priority: P3 → --
QA Contact: jbecerra
OS: Windows 8 Metro → Windows 8.1
Priority: -- → P2
Whiteboard: [defect] p=0 → p=0
Whiteboard: p=0 → [metro] p=0
Component: Input → Layout
Product: Firefox for Metro → Core
Version: unspecified → Trunk
Whiteboard: [metro] p=0 → [metro] p=0 [platform-rel-Facebook]
platform-rel: --- → ?
platform-rel: ? → ---
We never shipped the metro support, closing!
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.