Dnn.Platform icon indicating copy to clipboard operation
Dnn.Platform copied to clipboard

[Bug]: Parent Page Dropdown Crops Search Results on Page Details settings

Open dnndiva opened this issue 10 months ago • 8 comments

Is there an existing issue for this?

  • [x] I have searched the existing issues

What happened?

When using the search on Parent Page dropdown, the dropdown menu resizes incorrectly, and crops the results without any available means to scroll.

Image Image

Steps to reproduce?

  1. Go to Persona Bar > Content (First Icon) > Pages.
  2. Click on any page from the right column.
  3. Under the Details Tab, find Parent Page dropdown.
  4. Enter any text in the search box. e.g."A"

Current Behavior

The dropdown page-picker-content element getsheight:110px; and the dropdown results get cropped.

Image

Expected Behavior

For the dropdown window to not crop the dropdown.

Relevant log output


Anything else?

My ¢2: I am not sure how the height is being calculated, might it be a case of just changing height to min-height?

Affected Versions

9.13.6 (latest release), 9.13.7 (alpha), 10.0.0 (alpha)

What browsers are you seeing the problem on?

Chrome

Code of Conduct

  • [x] I agree to follow this project's Code of Conduct

dnndiva avatar Feb 18 '25 23:02 dnndiva

@valadas, should I close this issue? I am not sure who closes it and when.

dnndiva avatar Sep 25 '25 15:09 dnndiva

@dnndiva, I just tested it in DNN v10.01.01 RC1 and its still broken. What would be the reason for closing it?

Image

jeremy-farrance avatar Sep 25 '25 15:09 jeremy-farrance

Yeah, I think that is a valid issue...

valadas avatar Sep 25 '25 16:09 valadas

@jeremy-farrance, because it said it was added to a future patch, and I didn't know exactly what that meant.

dnndiva avatar Oct 01 '25 21:10 dnndiva

It just means that when someone tackles this, it could go in a patch release like 10.1.2 for instance... But it could also be in 10.1.3 or any other patch, just depends on having a fix in time. In other words, the fix is probably expected to be a non-breaking fix that does not add a new feature...

valadas avatar Oct 02 '25 00:10 valadas

Got it, @valadas. So long story short, you'd be the one to close the issue, right?

dnndiva avatar Oct 03 '25 14:10 dnndiva

@dnndiva well not necessarily me, but when a fix is submited and merged into the codebase, either by the last reviewer or automatically if the issue is referenced in the PR manually or by using special text in a commit or pr description like https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

valadas avatar Oct 03 '25 16:10 valadas

Thanks for the explanation, @valadas. 😊

dnndiva avatar Oct 06 '25 16:10 dnndiva