Closed Bug 1965069 Opened 9 months ago Closed 6 months ago

Drag-and-drop reordering of skills on LinkedIn does not complete

Categories

(Web Compatibility :: Site Reports, defect, P2)

Firefox 138
ARM64
macOS

Tracking

(Webcompat Priority:P2, Webcompat Score:6, firefox-esr128 unaffected, firefox-esr140 fixed, firefox138 wontfix, firefox139 wontfix, firefox140 wontfix, firefox141 wontfix, firefox142 verified)

VERIFIED FIXED
Webcompat Priority P2
Webcompat Score 6
Tracking Status
firefox-esr128 --- unaffected
firefox-esr140 --- fixed
firefox138 --- wontfix
firefox139 --- wontfix
firefox140 --- wontfix
firefox141 --- wontfix
firefox142 --- verified

People

(Reporter: caohfi7dh, Unassigned)

References

(Regression, )

Details

(Keywords: regression, webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat:sightline])

User Story

platform:windows,mac,linux
impact:feature-broken
configuration:general
affects:all
branch:release
diagnosis-team:layout
user-impact-score:300

Attachments

(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:138.0) Gecko/20100101 Firefox/138.0

Steps to reproduce:

  1. Open https://www.linkedin.com and log into your account
  2. Go to your profile and click the pencil icon in the Skills section to edit
  3. Click on the three dots and then Reorder
  4. Try to drag a skill to reorder it

Actual results:

The drag starts but the skill item snaps back to its original position—drop is not completed.

Expected results:

Dragging a skill should allow reordering it by dropping it into a new position, as it works in Chrome.

Summary: Drag-and-drop reordering of skills on LinkedIn does not complete in Firefox → Drag-and-drop reordering of skills on LinkedIn does not complete
OS: Unspecified → macOS
Hardware: Unspecified → ARM64
Attached image screencast.gif
Component: Untriaged → General

Thank you for the report. I was able to reproduce the issue on Win 11 ARM and Win 11 using Firefox build 140.0a1(20250508215032).
Marking issue as new for engineering input.

Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: tzsoldos
Whiteboard: [qa-triage-done-c140/b139]
QA Whiteboard: [qa-triage-done-c140/b139]
Whiteboard: [qa-triage-done-c140/b139]

Moving to Web Compat for investigation

Component: General → Site Reports
Product: Firefox → Web Compatibility
Severity: -- → S3
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: --- → 6
Priority: -- → P2
Whiteboard: [webcompat:sightline]
Flags: needinfo?(mrobinson)

Set release status flags based on info from the regressing bug 1918856

Flags: needinfo?(emilio)

Safari matches our behavior (https://commits.webkit.org/289431@main). Would be better to fix this in Chromium because our behavior follows the spec more closely.

A simple CSS intervention might be something like setting border-spacing: 0 0.1px or so on the relevant element, so that you get the two-value serialization...

Flags: needinfo?(mrobinson)

Blink does already match our behavior for specified shorthands, making it extra-silly: https://chromium-review.googlesource.com/c/chromium/src/+/6563724

Flags: needinfo?(emilio)

:mrobinson, since you are the author of the regressor, bug 1918856, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(mrobinson)

It seems that if all major browsers do the same thing here, we probably shouldn't revert this?

Flags: needinfo?(mrobinson)

Yeah to be clear chrome doesn't do the same, but only on the computed style. That's why I sent comment 7 their way.

Set release status flags based on info from the regressing bug 1918856

Can we add a WPT test for this?

Flags: needinfo?(emilio)

There are multiple, see css/css-tables/parsing/border-spacing-computed.html etc. Or you mean something else?

Flags: needinfo?(emilio) → needinfo?(jmuizelaar)

https://wpt.fyi/results/css/css-tables/parsing/border-spacing-computed.html?label=experimental&label=master&aligned shows Chrome passing all the tests. Could there be a test for the behaviour that we want Chrome to have that they fail?

Flags: needinfo?(jmuizelaar) → needinfo?(emilio)

That's because https://chromium-review.googlesource.com/c/chromium/src/+/6563724 landed, which made it pass, am I missing something?

Flags: needinfo?(emilio)

I think it is me that was confused. Is this correct?

Yes, the underlying bug LinkedIn is dependent on is fixed in chromium trunk but not release yet.

Looks like they fixed it, perhaps forced by Chrome updating and shipping

Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED

Verified as FIXED using the RC Build

Tested with:

Browser / Version: Firefox 142.0-candidate build 1
Operating System: Windows 10 PRO x64, Mac OSX 10.15

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: