Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop target for uploads (content and theme) is broken. #21439

Closed
1 task done
cathysarisky opened this issue Oct 28, 2024 · 5 comments · Fixed by #21687
Closed
1 task done

Drop target for uploads (content and theme) is broken. #21439

cathysarisky opened this issue Oct 28, 2024 · 5 comments · Fixed by #21687
Labels
bug [triage] something behaving unexpectedly P3 - Medium [triage] Bugs which we'll fix soon

Comments

@cathysarisky
Copy link
Contributor

cathysarisky commented Oct 28, 2024

Issue Summary

(Not a new issue - has been bugging me for months!)

The 'drop target' for drag and dropping a theme or upload file doesn't work right on Windows 10, Chrome browser. Occurs on local installs AND on Ghost Pro.

Image: Shows hovering over the 'drop area', but the cursor still shows 'copy', and if I drop it here, it'll download it (NOT upload it to Ghost).
image

Image: The very edge of the drop area (marked in yellow) is actually droppable. /IF/ I can get my cursor over this sliver between the dotted and solid borders, dropping works. The big red x area is not.
image

Chrome is up to date:
Version 130.0.6723.70 (Official Build) (64-bit)

UPDATE: See #21687 for more discussion . I think this is not actually a problem with the drop area, but with re-rendering. (Holding the mouse still for a long period seems to stop the rerenders, and targeting the edge was probably causing me to do that? I think?)

Steps to Reproduce

Use Chrome. (Possibly use Chrome on Windows - not sure.)
Attempt to drag and drop a file into the drop area for theme upload or import upload.

I expect the entire box to be a valid drop target.

Ghost Version

5.98 (and multiple versions before)

Node.js Version

18

How did you install Ghost?

various, including on Ghost Pro

Database type

MySQL 8

Browser & OS version

Chrome Version 130.0.6723.70 (Official Build) (64-bit)

Relevant log / error output

No response

Code of Conduct

  • I agree to be friendly and polite to people in this repository
@github-actions github-actions bot added the needs:triage [triage] this needs to be triaged by the Ghost team label Oct 28, 2024
@aarifkhan7
Copy link

Hey @cathysarisky,

I'm a beginner interested in contributing to open source, and this issue seems like a good starting point for me. Could you please assign it to me?

Thanks!

@cathysarisky
Copy link
Contributor Author

I'm a beginner interested in contributing to open source, and this issue seems like a good starting point for me. Could you please assign it to me?

Sorry, I don't have write-permissions on this repo so can't help you there. The Ghost dev team has said previously that they don't assign issues to new contributors, but you're welcome to put in a PR for it.

If you're currently using Ghost, you might like to head on over to the forum (https://forum.ghost.org) and introduce yourself, too!

@aarifkhan7
Copy link

It's fine, I will create a PR.

Thanks for the forum link, I will join it. :)

@sagzy sagzy added the P3 - Medium [triage] Bugs which we'll fix soon label Nov 5, 2024 — with Linear
@sagzy sagzy removed the needs:triage [triage] this needs to be triaged by the Ghost team label Nov 5, 2024
@sagzy sagzy added the bug [triage] something behaving unexpectedly label Nov 5, 2024 — with Linear
@9larsons
Copy link
Contributor

That's correct, we do not assign issues. If you want to fix it, just open a PR 👍.

@harshul786
Copy link

Submitted a PR to resolve this: #21440. Hope it helps—happy to tweak if needed! 🙌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug [triage] something behaving unexpectedly P3 - Medium [triage] Bugs which we'll fix soon
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants