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

proposed component: content-block #10

Open
BryanWilhite opened this issue Jun 2, 2020 · 4 comments
Open

proposed component: content-block #10

BryanWilhite opened this issue Jun 2, 2020 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@BryanWilhite
Copy link
Owner

BryanWilhite commented Jun 2, 2020

content-block defines a block DOM element that has the following features:

  • responsive awareness
  • opacity property/attribute
  • a collection of DOM elements to display
  • background image sources
@BryanWilhite BryanWilhite added the enhancement New feature or request label Jun 2, 2020
@BryanWilhite BryanWilhite self-assigned this Jun 2, 2020
@BryanWilhite BryanWilhite changed the title proposed component: content-frame proposed component: content-block Jun 4, 2020
@BryanWilhite
Copy link
Owner Author

i have changed the name to content-block because the word frame defines an instant of animation which clashes with our block here which could be associated with CSS animation

what distinguishes this block from any old DOM block is its ‘responsive awareness’

@BryanWilhite
Copy link
Owner Author

BryanWilhite commented Jun 7, 2020

‘responsive awareness’ is related to the orientation selector in CSS [MDN]:

image

This CSS-based feature comes with this note:

This feature does not correspond to device orientation. Opening the soft keyboard on many devices in portrait orientation will cause the viewport to become wider than it is tall, thereby causing the browser to use landscape styles instead of portrait.

this strongly suggests to me that JavaScript is the reliable alternative when device orientation is needed over CSS flow layout orientation

@BryanWilhite
Copy link
Owner Author

BryanWilhite commented Jun 7, 2020

the ‘collection of DOM elements’ must be generated from data (likely JSON) it is this fundamental requirement that is the most challenging (and distracting)

my previous songhay-core issue surely must be related to this requirement as it reminds me that markdown and HTML strings are ‘display text’

i am not clearly seeing how ‘display text’ and my newly-found LitElement-enhanced template literals can all work together

🔍 https://github.com/YerkoPalma/marli

@BryanWilhite
Copy link
Owner Author

The Songhay Progressive Audio Player has to have something to offer for this effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant