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

Pointer link in table cell been cover by other cell #3774

Closed
leofcshen opened this issue Oct 10, 2022 · 1 comment
Closed

Pointer link in table cell been cover by other cell #3774

leofcshen opened this issue Oct 10, 2022 · 1 comment
Labels
Milestone

Comments

@leofcshen
Copy link

Describe the Bug

I try to set a p tag with id in a table cell like below for reuse this cell content.
I can reuse this table cell successful In other content with {{@page_id#content_id}} .
But when I select the cell, the pop-up pointer link is covered by up cell.

Steps to Reproduce

<tr style="height: 30.1094px;">
<td style="height: 30.1094px;">test</td>
<td style="height: 30.1094px;">
<p id="bkmrk-1"><code>F11</code></p>
</td>
<td style="height: 30.1094px;">comment</td>
</tr>

1.Select cell without setting p tag and id, pop-up pointer link normally (the default reference all table)
擷取

2.Select cell with setting p tag and id, pop-up pointer link was covered by up cell.
擷取
螢幕擷取畫面 2022-10-10 143911 PNG

Expected Behaviour

pop-up pointer link normally in table cell

Screenshots or Additional Context

No response

Browser Details

Chrome 105.0.5195.127(64-bit) on Windows 10

Exact BookStack Version

v22.07.3

PHP Version

No response

Hosting Environment

docker container

ssddanbrown added a commit that referenced this issue Oct 18, 2022
Avoids interferance with elements that have their own overflow behaviour
such as table cells.
Related to #3774
@ssddanbrown ssddanbrown added this to the Next Feature Release milestone Oct 18, 2022
@ssddanbrown
Copy link
Member

Thanks for reporting @leofcshen, and thanks for providing clear replication guidance.
Seemed to be something that was not an issue on Firefox but could replicate as described on chrome.
This has been addressed in d084f22 and will be part of the next feature release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants