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

[RESEARCH] Desktop ready general solution for pressed state #1867

Closed
5 tasks
Tracked by #2010
RasmusKjeldgaard opened this issue Nov 4, 2021 · 1 comment
Closed
5 tasks
Tracked by #2010
Assignees
Labels
enhancement New feature or request Web

Comments

@RasmusKjeldgaard
Copy link
Collaborator

Describe why and what should be researched

As part of the work of making the Kirby Components Desktop Ready, it would make sense to research if it is possible to make general solutions for various interactivity states, before beginning implementing component specific solutions. This issue is concerned with pressed state (active pseudo selector).

Considerations

The following is worth considering when researching

Design:

  • Background color?
  • Border?
  • Shadow?

Implementation:

  • Investigate differences between components, to see if we can make a generalized solution.
  • Prioritise general solution in html and css (directives will have to be rewritten later when moving to web-components)

Describe the goal

To unearth problems and consider if it is possible to come up with a (potentially partially) general solution for implementing the interactivity state. If possible also a POC of the solution.

@RasmusKjeldgaard RasmusKjeldgaard added enhancement New feature or request NOT Tech refined Needs Tech kickoff - solution outlined and agreed NOT Prioritized Issue not yet prioritized and added to a Milestone 👶🏻 New For new issues before prioritisation and refinement labels Nov 4, 2021
@RasmusKjeldgaard RasmusKjeldgaard removed NOT Tech refined Needs Tech kickoff - solution outlined and agreed NOT Prioritized Issue not yet prioritized and added to a Milestone 👶🏻 New For new issues before prioritisation and refinement labels Nov 4, 2021
@alxzak alxzak added the Web label Dec 3, 2021
@alxzak alxzak added this to the M11 milestone Jan 19, 2022
@alxzak alxzak added this to Kirby Mar 4, 2022
@alxzak alxzak modified the milestones: M11 ( 27/1 - 6/4 ), M12 ( 7/4 - 15/6) Mar 7, 2022
@jkaltoft jkaltoft modified the milestones: M12 ( 7/4 - 15/6), 🧪 Interaction States Mar 29, 2022
@jkaltoft jkaltoft moved this to 💡 Shaping in Kirby Mar 29, 2022
@jkaltoft jkaltoft removed the status in Kirby Mar 29, 2022
@jkaltoft jkaltoft self-assigned this Mar 29, 2022
@jkaltoft jkaltoft moved this to 💡 Shaping in Kirby Mar 29, 2022
@jkaltoft
Copy link
Collaborator

Conclusion

  • Create a mixin for a general solution similar to apply-hover()
  • Create customised solutions as needed
    • Based on experience with the other interaction states it's not realistic to expect to find a single solution for all components

Repository owner moved this from 💡 Shaping to ✅ Done in Kirby Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Web
Projects
Archived in project
Development

No branches or pull requests

3 participants