Scroll issue on Glossary related entity page

[Ankit-Keshari-Vituity]

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[Ankit-Keshari-Vituity]

[github-actions]

Unit Test Results (build & test)

517 tests  ±0   517 ✔️ ±0   8m 22s ⏱️ -48s
121 suites ±0       0 💤 ±0 
121 files   ±0       0 ❌ ±0 

Results for commit 7956a63. ± Comparison against base commit 42a847c.

♻️ This comment has been updated with latest results.

[chriscollins3456]

what about any of the other batch actions? like setting domains and other bulk situations this will only fix the css issue if it's glossary terms.

[chriscollins3456]

removing this CSS makes me nervous as this will affect many other places in the code. It appears that the only place affected by this weird double scroll situation is the glossary related entity tab, while other places using this component are totally fine.

It's because of that that I would suggest changing GlossaryRelatedEntity instead of changing this component that usually looks good.

I tested locally and if you simply change the return of GlossaryRelatedEntity.tsx from:

    return (
        <GroupAssetsWrapper>
            <Col md={24} lg={24} xl={24}>
                <EmbeddedListSearchSection
                    fixedQuery={fixedQueryString}
                    emptySearchQuery="*"
                    placeholderText="Filter entities..."
                />
            </Col>
        </GroupAssetsWrapper>
    );

to:

    return (
        <EmbeddedListSearchSection
            fixedQuery={fixedQueryString}
            emptySearchQuery="*"
            placeholderText="Filter entities..."
        />
    );

your problem is fixed

[chriscollins3456]

nice!