Drag-and-drop reordering of skills on LinkedIn does not complete
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:6, 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)
|
735.15 KB,
image/gif
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:138.0) Gecko/20100101 Firefox/138.0
Steps to reproduce:
- Open https://www.linkedin.com and log into your account
- Go to your profile and click the pencil icon in the Skills section to edit
- Click on the three dots and then Reorder
- 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.
Comment 2•9 months ago
•
|
||
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.
Updated•9 months ago
|
Updated•9 months ago
|
Comment 3•9 months ago
|
||
Moving to Web Compat for investigation
Updated•9 months ago
|
Updated•9 months ago
|
Comment 4•9 months ago
|
||
mozregression led me to https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=962f032aff105cd8340964e5702ef2186d15ed46&tochange=3c952710a4cd42c0b793e191e7ee0909430fd846
So Bug 1918856 regressed this, I am moving this layout team's radar.
Updated•9 months ago
|
Comment 5•9 months ago
|
||
Set release status flags based on info from the regressing bug 1918856
Updated•9 months ago
|
Updated•8 months ago
|
Comment 6•8 months ago
|
||
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...
Comment 7•8 months ago
|
||
Blink does already match our behavior for specified shorthands, making it extra-silly: https://chromium-review.googlesource.com/c/chromium/src/+/6563724
Comment 8•8 months ago
|
||
:mrobinson, since you are the author of the regressor, bug 1918856, could you take a look?
For more information, please visit BugBot documentation.
Comment 9•8 months ago
|
||
It seems that if all major browsers do the same thing here, we probably shouldn't revert this?
Comment 10•8 months ago
|
||
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.
Comment 11•8 months ago
|
||
Set release status flags based on info from the regressing bug 1918856
Comment 13•8 months ago
|
||
There are multiple, see css/css-tables/parsing/border-spacing-computed.html etc. Or you mean something else?
Comment 14•8 months ago
|
||
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?
Comment 15•8 months ago
|
||
That's because https://chromium-review.googlesource.com/c/chromium/src/+/6563724 landed, which made it pass, am I missing something?
Comment 16•8 months ago
|
||
I think it is me that was confused. Is this correct?
- Chrome release currently has the behaviour that LinkedIn expects.
- Chrome changed their behaviour to match ours in https://chromium-review.googlesource.com/c/chromium/src/+/6563724
- Once that ships linkedin will break in Chrome too
Comment 17•8 months ago
|
||
Yes, the underlying bug LinkedIn is dependent on is fixed in chromium trunk but not release yet.
Updated•8 months ago
|
Updated•8 months ago
|
Updated•7 months ago
|
Updated•7 months ago
|
Comment 18•6 months ago
|
||
Looks like they fixed it, perhaps forced by Chrome updating and shipping
Comment 19•5 months ago
|
||
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
Updated•5 months ago
|
Updated•5 months ago
|
Description
•