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

mat/cdk-split-view component #7940

Open
jorroll opened this issue Oct 21, 2017 · 3 comments
Open

mat/cdk-split-view component #7940

jorroll opened this issue Oct 21, 2017 · 3 comments
Labels
area: new Issues requesting a new component or area feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@jorroll
Copy link

jorroll commented Oct 21, 2017

feature request: mat-split-view/cdk-split-view component

screen-shot-2017-10-21-at-1 45

See bertrandg/angular-split for inspiration.

What is the expected behavior?

In more complex applications, split views (allowing the user to resize the views) are a great way of handling users with different sized displays each viewing content of differing proportions. By giving the split views angular bindings, the component becomes incredibly flexible

  • Ability to dynamically split content vertically, or horizontally, or with multiple, nested levels.
  • Ability for user to drag divider to adjust container sizing
  • Ability to fix sizing of some containers (preventing user from adjusting the size)
  • Ability to animate container resizing
  • Built in method for handling / adapting to mobile views vs tablet views vs destop views
  • Ability to programmatically adjust container size

What is the current behavior?

There is at least one third party library offering some of this functionality (bertrandg/angular-split).

What is the use-case or motivation for changing an existing behavior?

I think the material team could improve upon this foundation by ensuring mat-split-view "plays nice" with other material components, by ensuring it is accessible on multiple devices / screen readers, by ensuring split-views can respond to text direction changes, and by providing an elegant way of repositioning content for desktop screens vs mobile screens.

Even for applications that don't want users to be able to dynamically resize views, a well designed mat-split-view component could be an easy way for devs to layout content and interact with containers (including "opening" / "closing" views when a button is clicked).

Is there anything else we should know?

This is probably a "cdk" component rather then "material" component. Not sure if this proposal should be placed somewhere else.
Also: I enlarged the mouse-cursor icon for legibility

@jelbourn jelbourn added discussion feature This issue represents a new feature or feature request rather than a bug or bug fix P5 The team acknowledges the request but does not plan to address it, it remains open for discussion labels Oct 29, 2017
@josephperrott
Copy link
Member

Note: If/when this feature is implemented, it should be implemented in CDK and available in Material.

@josephperrott josephperrott reopened this Mar 26, 2018
@jorroll jorroll changed the title mat-split-view component mat-split-view/cdk-split-view component Mar 26, 2018
@jorroll jorroll changed the title mat-split-view/cdk-split-view component mat/cdk-split-view component Mar 26, 2018
@mmalerba mmalerba added needs: discussion Further discussion with the team is needed before proceeding and removed discussion labels Mar 3, 2020
@andrewseguin andrewseguin added the area: new Issues requesting a new component or area label Jun 11, 2020
@ahnpnl
Copy link

ahnpnl commented Jul 29, 2020

I'm looking forward to this feature. Horizontal/vertical splitter is commonly used on web apps nowadays

@eamon-otuathail
Copy link

This is a very good suggestion. It would make an Angular app better able to run on different screen sizes and have the user in control of pane sizes within each of the splitter's panes. See how splitters works well within Visual Studio Code for a practical example of how splitters should work. .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: new Issues requesting a new component or area feature This issue represents a new feature or feature request rather than a bug or bug fix needs: discussion Further discussion with the team is needed before proceeding P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Development

No branches or pull requests

7 participants