(this issue)

Material Design guidelines don't specify popovers, but the specification of material properties provide a clear set of properties that can be used to create popups.

No more waiting around for pull requests to be merged and published. No more forking repos just to fix that one tiny thing preventing your app from working.

Yarn only runs the postinstall hook after yarn and yarn add, but not after yarn remove. The postinstall-postinstall package is used to make sure your postinstall hook gets executed even after a yarn remove.

It seems being able to bind:this={slotEl} directly on a slot element is a popular request. I'll add my +1 as adding div wrappers just to get dom references gets old really fast.

I also would like to see any hidden blocks or dev shortcuts.

I'm more bothered by the fact that you can't practice other people's levels, just certain parts of the level, before actually going back and trying to beat it completely.

I hope @hperrin you're still alive to discuss about this and eventually for a pull request.

@monkeythedev I am curious how do you "organize" your work - You forked https://github.com/hperrin/svelte-material-ui and https://github.com/hperrin/svelte-material-ui is not very active. Do you plan an independent project ? I hope the original author would return at some times, if not, i'll see

Maybe @hperrin would be able to make an appearance and select a few additional maintainers to help out.

You can also see this repo: default-passive-events.

After some attempts mapping with Svelte, I missed using canvas instead of SVG

In the past, I tried to create some proof of concepts with svelte, but I usually ended up missing some of the features that RxJS provides. Now that I know that they complement each other well, I will grab this combination more often

Not being cancelable makes validating dialog content impossible - eg a login dialog or anything that takes user input. Of course, it's easy enough to get around - but I think this should be a requirement of a dialog.

It used to be great that I was able to select a layer from any image and use it as a starting point. Currently, I am given an image that has 4 layers to be stripped off to get to the original base image. The original image is not reconstructable in any other way.

# Run once, hold otherwise if [ -f "already_ran" ]; then echo "Already ran the Entrypoint once. Holding indefinitely for debugging." cat fi touch already_ran

Edit this file (corresponding to your stopped container): vi /var/lib/docker/containers/923...4f6/config.json Change the "Path" parameter to point at your new command, e.g. /bin/bash. You may also set the "Args" parameter to pass arguments to the command. Restart the docker service (note this will stop all running containers):

I refuse to back anything from Queen games. Their kickstarters, IMO, are meant to get people to have FOMO instead of something being worth the price.

I came over from Vue as well, the out-in is one thing I miss with Svelte. Rich Harris even acknowledged it prior to Svelte 3 but never really implemented a fix as far as I'm aware.

Directives like ng-if="info.report.revenue" sort of work in Angular if info.report is undefined, in that the ng-if becomes false. But the Svelte equivalent {#if info.report.revenue} throws an error. For now we're using lodash get in places where we need to and looking forward to Svelte support for optional chaining.

Since you've been using Svelte for a few months after using React, haven't you been hit by the lack of composability in Svelte?Passing around components as variables is such a common pattern in React, and there's no good replacement in Svelte. The lack of dynamism in components and styles makes theming and crafting reusable components (outside of simple widgets) very tedious [1][2]. I'm genuinely curious how someone can come from React and not be bothered by it.

If this is getting implemented, I think I'll love to see both implemented. I can see a lot of use cases where I would like to encapsulate the component with additional wrappers and in another scenarios I would like to just use the component. Now i work around this using empty div but then at times it breaks the structure because of the div element and I'll have to add more class utilities to make it work. This will be a great addition for Svelte.

I also tried to use <!-- svelte-ignore unused-export-let --> before the script tag but still no chance.

You can only adopt a workaround, which can be one of

I use a mutator and use it's changeValue function to 'change' the value of the relevant field (I supply the same value). This in turn notifies all relevant parties of the change to the form's state, and a validation is triggered.

Use the same value that was submitted, which ensures that a 'change' is triggered even though the value itself doesn't change. Therefore, the same value gets validated again.

  mutateValue([name], state, { changeValue }) {
    // change the value to the same value, thus
    // triggering a revalidation of the same value
    changeValue(state, name, value => value);
  }

I have a feature spec to test the Javascript behavior of the blur event, sadly Capybara's native DSL doesn't seem to support it yet.

mixing the turing complete of javascript with the markup of HTML eliminates the readability of JSX so that it is actually harder to parse than a solution like hyperscript

I discovered that a solution can be hacked using an {#if}, but a proper one would be nice:

This reactive statement is just used to have the store automatically subscribed and unsubscribed.

the code is a bit verbose/convoluted

Using another reactive statement with $effect we have Svelte automatically handle subscribing and unsubscribing to the store

It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.

Here's a proxy store I wrote to derive the value of a store nested within other stores, it plays nice with typescript and can go infinitely deep

I guess we could always add a bunch of adapter code to watch the flag and trigger a callback when it becomes true or false...

but would it be reasonable to expect svelte-select to handle that so that consumers of this lib don't have to do all that?

Most simple example: <script> import ChildComponent from './Child.svelte'; </script> <style> .class-to-add { background-color: tomato; } </style> <ChildComponent class="class-to-add" /> ...compiles to CSS without the class-to-add declaration, as svelte currently does not recognize the class name as being used. I'd expect class-to-add is bundled with all nested style declarations class-to-add is passed to ChildComponent as class-to-add svelte-HASH This looks like a bug / missing feature to me.

Vue does this in a way that just makes sense.

Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.

There's no way to change style incapsulation method without patching the compiler, and this means maintaing a fork, which is not desirable.

The problem with working around the current limitations of Svelte style (:global, svelte:head, external styles or various wild card selectors) is that the API is uglier, bigger, harder to explain AND it loses one of the best features of Svelte IMO - contextual style encapsulation. I can understand that CSS classes are a bit uncontrollable, but this type of blocking will just push developers to work around it and create worse solutions.

Ideally, you should be able to write pure css in style tags in components, just like you can other frameworks(React or vue)

being able to compose multiple components' functionality via decoration (not creating new "combo" components or something) is more elegant, and something I wish React had.

Seems a little unfortunate that there is no obvious way to edit or remove my previous reply.

With inline diff tags you can display {+ additions +} or [- deletions -].

I want my Page Translator extension to be made irrelevant by Firefox having built-in language translation, like Google Chrome and Microsoft Edge. It is a critical feature used by millions of people daily. It bridged a feature gap. Mozilla killing this add-on without replacing it hurts users.

I would love for Mozilla to make this extension irrelevant by providing the functionality natively. Language translation is a standard and yet highly differentiating feature in Chrome and Edge.

I wish Mozilla would recognize the importance of built-in translation that Google Chrome and Microsoft Edge have.

Some variety of markdown support the following syntax, but not supported in Hugo/BlackFriday. [Lua Software](http://www.luasoftware.com){:target="_blank"}

[link](url){:target="_blank"} Works for jekyll or more specifically kramdown, which is a superset of markdown, as part of Jekyll's (default) configuration. But not for plain markdown. ^_^

For ghost markdown use: [Google](https://google.com" target="_blank) Found it here: https://cmatskas.com/open-external-links-in-a-new-window-ghost/

No more struggling to stay on top of every little thing your team is saying, for fear of missing out.

Some questions are only asked by people with a fundamental misunderstanding. The friends who walk into my office and ask, “have you read all of these” miss the point of books.

FYI for later travellers, it looks like the comment in question by @FreeSoftwareServer has been removed.

Thank you, I put the restaurant_params both in def new & def create but only need it in the def create

This being the City of Ryde, political vendettas are never far from the surface.

It is also possible to use this annotator to annotate fields other than the NamedEntityTagAnnotation field by and providing the header

can not

arrived.

n m

Some Lifetime Prevalence Results From the National Comorbidity Survey

craniocervical junction compression

For the moment I’ll put on my scientific thinking hat because there numerous ways that I can provide evidence for my claim the people believe all sorts of crazy things.

Miss Amazing is a pageant for girls and young women with learning disabilities. In the 10 years since it began, 1,700 girls and young women with disabilities have taken part.Pageant Has Spread To More Than 30 States

A third might leave the experience out of his story altogether, deeming it unimportant.

Three of the victims were of Turkish origin,[38] two victims were from German Sinti families and one from a Kosovan Roma family.

VFT

It also

XXX More stuff here

Does the Espionage Act violate the First Amendment guarantee of free speech?

Reproducibility