Hi, maybe someone has run into this.
I'm noticing that download and target attributes are not getting removed
from links even though subsequent renders are omitting them.
Using this test code on http://elm-lang.org/try:
import Html exposing (a, text, beginnerProgram)
import Html.Events
This is surprising… Looks like DOM↔VDOM diff does not remove missing (but
attached once) attributes? Or it ignores them because it does not want to
be too invasive?
As a other workaround, you can have always two amchor tags: one with
"target", one without, and just switch the visibility of them
On Tuesday, May 9, 2017 at 8:36:37 AM UTC+1, Gusztáv Szikszai wrote:
>
> I'm glad it worked :) I need to figure out something for the install
> problem though, probably will find an other place where the binary can be
> stored.
>
Its strange that when running "npm install -g elm-github-install"
> I have my examples/elm-package.json include ../src, and have my CI script
> build all the examples so that I remember to update the examples of the API
> changes.
>
> Also, imo it's good to have a separate examples/elm-package.json because
> you often want other dependencies to make a
A personal pain point of mine is when the examples just import TheModule
exposing (..) rather than just using fully qualified references
TheModule.aFunction .
First of all, because that's not how the library will be used.
Second, and more important, unless you know already what the library
Ah yes, that's another good workaround.
It's definitely not rendering as I would expect. Probably a performance
optimization that's gone awry.
I also tried download False, but that renders download="false". Which also
triggers a download (!) instead of opening normally, so the Elm's download
On Tuesday, May 9, 2017 at 2:46:06 AM UTC+1, Ian Mackenzie wrote:
>
> In general, yes, using matrices would likely be a bit more efficient, but
> you can get pretty close using techniques like the above, and I think the
> expressiveness/clarity/flexibility is better.
>
Thanks for this
I'm glad it worked :) I need to figure out something for the install
problem though, probably will find an other place where the binary can be
stored.
On Monday, May 8, 2017 at 11:25:31 PM UTC+2, Rupert Smith wrote:
>
> On Monday, May 8, 2017 at 8:39:57 PM UTC+1, Rupert Smith wrote:
>>
>> On
"Waiting for Evan". I've heard that before!
https://www.youtube.com/watch?v=Wifcyo64n-w
On Sunday, May 7, 2017 at 4:12:34 AM UTC+2, Kasey Speakman wrote:
>
> I don't think there are new native packages being approved. In fact, I
> think more are to get cut soon. We will just have to wait on
