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

Compatibility check and testing for Responsive Design (jsonConfig) #39

Open
ioBroker-Bot opened this issue Oct 15, 2024 · 2 comments
Open

Comments

@ioBroker-Bot
Copy link

Notification from ioBroker Check and Service Bot

Dear Adapter developer,

ioBroker should be fully usable and operable on mobile devices

So please check your adapter jsonConfig for Responsive Design.
You can perform these tests in the developer console of your browser (F12)


For jsonConfig, all resolutions should be taken into account in the respective inputs.

The following resolutions are provided:

  • xl - width in 1/12 of screen on extra large screens (1536px < width)
  • lg - width in 1/12 of screen on large screens (1200px <= width < 1536px)
  • md - width in 1/12 of screen on middle screens (900px <= width < 1200px)
  • sm - width in 1/12 of screen on small screen (600px <= width < 900px)
  • xs - width in 1/12 of screen on tiny screens (width < 600px)

We recommend the following values for the standard layout

"xs": 12,
"sm": 12,
"md": 6,
"lg": 4,
"xl": 4

The following entry should be made below "type": "tabs" in order to display a clearly legible table bar:

"tabsStyle": {
  width: "calc(100% - 100px)"
},

Please close the issue after you checked it.

Feel free to contact me (@ioBroker-Bot) if you have any questions.

And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.

your
ioBroker Check and Service Bot

@simatec for evidence

Note: If you added Responsive Design tests already, simply close this issue.

Copy link

stale bot commented Nov 16, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale Issue has not beed updated for long time. label Nov 16, 2024
@mcm1957
Copy link
Contributor

mcm1957 commented Nov 16, 2024

This issue should not be considered stale as it is not yet processed.

@stale stale bot removed the stale Issue has not beed updated for long time. label Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants