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

Scroll is disabled on Connector Set Up page on a specific doc panel width #13735

Closed
erica-airbyte opened this issue Jun 13, 2022 · 1 comment · Fixed by #14531
Closed

Scroll is disabled on Connector Set Up page on a specific doc panel width #13735

erica-airbyte opened this issue Jun 13, 2022 · 1 comment · Fixed by #14531
Assignees
Labels
area/frontend Related to the Airbyte webapp autoteam needs-triage type/bug Something isn't working

Comments

@erica-airbyte
Copy link
Contributor

erica-airbyte commented Jun 13, 2022

Environment

Cloud / OSS

Current Behavior

The connector set up page will not scroll when the doc panel on the right is at a specific width. This is easy to reproduce when dev tools is open. (recording can be provided on request).

You can scroll the knowledge base on the page but not the connector set up.

Expected Behavior

Be able to scroll a page when dev tools is open.

Steps to Reproduce

  1. Select "Set up Source/destination"
  2. Choose source/dest. to set up (Bigquery is a good one since it has a long set up page)
  3. On the connector set up page open up developer tools and try and scroll down the page.
  4. The page scroll is not possible.
@octavia-squidington-iii
Copy link
Collaborator

cc @airbytehq/frontend

@edmundito edmundito changed the title Scroll Disabled on Connector Set Up page when Dev Tools is open Scroll is disabled on Connector Set Up page on a specific doc panel width Jul 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/frontend Related to the Airbyte webapp autoteam needs-triage type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants