-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Long click on hyper link at bottom it display some background shadow - reported by @dharmik #7796
Comments
Triggered auto assignment to @JmillsExpensify ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
@JmillsExpensify I think a lot of process steps got skipped. This is not triaged yet. |
Oh yeah I see what you mean. I'm so used to the External label for this repo but I was assigned for Triage. I'll hide the Upwork job for now. |
Triggered auto assignment to @nkuoch ( |
Proposal: FileName: TextLink.js
|
Double checking with @AndrewGable if this is something we want to fix? |
Proposal: |
I agree I am not sure I see the bug here, looks to be working as expected? |
Ah yeah I don't think this is critical, but there is no feedback on hover over for the link/URL. That's how I interpreted this issue, that it's inconsistent with the behavior for links. I'm not super passionate either way though. |
Got it - So we should have no shadow on long press on mobile because there is no hover feedback for web? That makes sense if so! |
Let's see what @shawnborton thinks before moving forward. |
Just to confirm, this only happens when you long-tap? Just a simple tap doesn't launch the bg color right? I kind of think this is fine as it is. I suppose we could even actually keep the behavior but specify the background color we want. |
This is super minor stuff, to be clear. That said, we also approach the links differently on OldDot versus NewDot. On desktop, OldDot changes color to provide feedback, whereas NewDot is static (no feedback). Then on mobile, long tapping the homepage link on OldDot uses the existing background, whereas on NewDot we use a grey background. So really whatever we do, we should probably make it consistent. |
Another matter entirely is whether this is important enough to do anything. I originally thought this was good for consistency, but I also could see the argument that this is so minor and we have more important pursuits that we can also choose to close the issue. |
I like the idea of treating long-press on mobile/tablets the same as :hover on desktop, and then aligning the desired effect between both behaviors. |
Going to put a monthly on this and came back to it. It's not a priority for now. |
Focused on another stuff right now. |
I'm just going to close this and we can re-open down the line when details like this are more important. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
Long press that background shadow must not be there
Actual Result:
Long press that background shadow is there
Workaround:
unknown
Platform:
Where is this issue occurring?
Version Number: 1.1.38-0
Reproducible in staging?: Y
Reproducible in production?: Y
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.2022-02-04.at.12.05.05.AM.mov
Expensify/Expensify Issue URL:
Issue reported by: @dharmik
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1643913495412989
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: