DivMagic VS material-ui-docs

I'm currently working on an extension as well ([0]) and share the same concerns many have mentioned about extensions here. I'd like to highlight another dimension concerning the Browser APIs ([1]).

Handling the permissions necessary for certain API functionalities and the corresponding warning messages can be somewhat confusing. For instance, our extension uses "chrome.devtools.panels" to open a new window within DevTools. This API doesn't require any permissions by itself. Yet, for messaging across the popup, content, and DevTools windows, we're required to use activeTab and sendMessage APIs. The DevTools window operates in its unique context, almost like a tab within another tab. For example, updating the URL in the active tab doesn't directly update the DevTools window but triggers an event.

Messaging across these different contexts requires the "https://*/*" host permission, without which Chrome and Firefox won't send the messages between these isolated windows.

We made this permission optional, the DevTools Panel is activated only upon receiving explicit user consent. However, the permission prompt's messaging is something like "This extension requires access to all your data," which sounds very alarming. We don't access any data nor that we want to, but requiring that permission is mandatory since the message APIs won't work without them.

This is just one example of the many undocumented complexities within Chrome's documentation. Similar pitfalls exist with message exchanges between the background service and content scripts. Sometimes you don't know why your API call doesn't work even though you think you have the required permission and asking for more permissions show very alarming messages to users.

I think that a more granular permission approach, made specific to API functionalities rather than broad permissions that cover a list of APIs, would significantly help user experience. For example, requesting permission for the "sendMessage API" with a clear explanation would be far more informative for users than the general "All host https:///" permissions.

There's also the issue of building for different browser. The same browser API calls can have different permissions requirement on Chrome and Firefox which makes the development process more difficult and more confusing for users since the same extension requires different permissions on different browsers.

[0] https://divmagic.com

You can see more demo videos here: https://divmagic.com

It doesn't need to be designed with Tailwind, just use DivMagic and convert it to Tailwind!

This is really Tailwind before Tailwind. I didn't know about it.

I'm working on a css style copying project on the side (DivMagic https://divmagic.com/) and I might add Tachyons as an option there

You can use DivMagic (https://divmagic.com)

I created a tool (DivMagic) which lets you copy any element from any website and convert it into HTML/JSX(React)/CSS/Tailwind CSS component.

You can make use of a tool like DivMagic (https://divmagic.com) to convert elements into inline CSS components

Wanted to shamelessly plug my tool here: DivMagic (https://divmagic.com)

I’m a big fan of Tailwind. I’d encourage you to checkout a tool called DivMagic. It allows you to copy any element from any website and paste them as tailwind components in your codebase. Super useful for building front ends quickly. Feels like a cheat code.

If none of the provided solutions work any you need to convert Tailwind CSS to inline raw CSS, you can make use of a tool like DivMagic (https://divmagic.com) to handle the conversion easily

I'll be using Material UI for styling the cards. You can install it by visiting the Material UI installation guide.

For the UI, MUI is a huge time saver. It's open-core and thoroughly excellent: https://mui.com/

They also have a lot of pre-built dashboards that tie into various cloud vendors (typically not FOSS though).

(My opinion only, please treat it as just one person's thought process, not some eternal truth)

As a frontend dev, for me it's primarily just an ecosystem thing. There's nothing wrong with HTMX or any other solution, like Ruby on Rails or Hotwire or even other JS frameworks like Angular or Gatsby, but they are not really what I see in the majority of the web dev ecosystem.

By ecosystem, I mean this:

- Developers are easy to find & hire for, and can work on existing code without much training because there are (relatively) standardized practices

- For any common problem, I can easily reuse (or at least learn from the source for) a package on NPM

- For any uncommon problem, I can find multiple robust discussion about it on various forums, Stack, etc. And ChatGPT probably has a workable overview.

- I can reasonably expect medium-term robust vendor support, not just from the framework developers but various hosts, third-party commercial offerings (routers, state management, UI libs, CMSes, etc.), i.e., it's going to stay a viable ecosystem for 3-5 years at least

- I don't have to reinvent the wheel for every new project / client, and can spin up a working prototype in a few minutes using boilerplates and 1-click deploys

I've been building websites since I was a kid some 30 years ago, first using Perl and cgi-bin and then PHP, and evolved my stack with it over time.

I've never been as productive as I am in the modern React ecosystem, especially with Next or Vite + MUI (https://mui.com/). Primarily this is because it allows me to build on top of other people's work and spend time only on the business logic of my app, at a very high level of abstraction (business components) and with a very high likelihood of being able find drop-in solutions for most common needs. I'm not reinventing the wheel constantly, or dealing with low-level constructs like manually updating the DOM. Or worse, dealing with server issues or updating OS packages.

What used to take days/weeks of setup now takes one click and two minutes, and I can have a useable prototype up in 2-3 hours. Because 95%+ of my codebase isn't mine anymore; I can just reuse what someone else built, and then reframe it for my own needs. And when someone else needs to continue the work, they can just pick up where I left off with minimal onboarding, because they probably already have React knowledge.

I think React, for all its faults, has just reached a point of saturation where it's like the old "nobody ever got fired for buying IBM", i.e., it's a safe, proven bet for most use cases. It may or may not be the BEST bet for any project, but it's probably good enough that it would at least warrant consideration, especially if the other stacks have less community/ecosystem support.

Explore Material UI: Material UI Documentation

- UI kit (I personally have good experience with React Material UI - https://mui.com/; there is also https://tanstack.com/)

the network is settled (I got the code from some discussion group). But nothing works. Playwright has also

page.waitForLoadState({ waitUntil: "domcontentloaded" }); etc.

but they are not working for my test cases.

2)

I have noticed that https://mui.com/ have dropdown menus, which implementation is far from normal html option. Mui uses some kind

MUI | Remote UTC-6 to +5 | Multiple roles | Full time | https://mui.com/

I'm a co-founder and the CEO of MUI. Our objective in the short term is to become the UI toolkit for React, unifying the fragmented ecosystem of dependencies into a single set of simple, beautiful, consistent, and accessible React components. In the longer term, our goal is to make building great web UIs quicker, simpler, and accessible to more people through a low-code platform for developers.

Some things we’re proud of:

- 25% of the downloads that React receives.

- 1M developers on our documentation every month.

- Solid financials: profitable

If this sounds interesting to you, we are hiring for: UI Engineers, Product Engineers, Developer Advocate / Content Engineer:

Here, at Woovi, our design system has been wrote using [MUI](https://mui.com/. But, in my opinion, I have some pain points considering how MUI built their components, most focusing on the fact of how they expose their component APIs and how they handle the component structure.

My feeling as a frontend dev was that Material Design You is just run of the mill enshittification at Google. Around the time that came out, Google also started to hide more buttons in the UI, made the drop down shade much more clumsy, got rid of the excellent Pixel fingerprint scanner, etc.

It felt to me like some other busy body design team had to show innovation and so made Material You adopt your wallpaper colors (in some ugly variation). It was like the MySpaceification of Android.

Material Design spawned some of my favorite projects, like MUI: https://mui.com/

That tracks Material v2 (pre you) and IMO is the best web UI currently available. There's some tentative work on adding Material You, but I hope they don't. It's a step backward IMO, form over function and against the original spirit of Material as a usability design library. https://github.com/mui/material-ui/issues/29345

5.material-ui