This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (5)
- # alda (1)
- # aws-lambda (1)
- # beginners (74)
- # boot (62)
- # cider (29)
- # cljs-dev (36)
- # cljsjs (15)
- # cljsrn (34)
- # clojure (58)
- # clojure-android (3)
- # clojure-austin (15)
- # clojure-austria (11)
- # clojure-dusseldorf (25)
- # clojure-germany (6)
- # clojure-greece (26)
- # clojure-quebec (8)
- # clojure-russia (50)
- # clojure-spec (12)
- # clojure-uk (8)
- # clojurescript (46)
- # core-async (11)
- # cursive (22)
- # datomic (2)
- # devcards (27)
- # dirac (5)
- # hoplon (109)
- # jobs (1)
- # kekkonen (2)
- # lein-figwheel (12)
- # leiningen (2)
- # microservices (1)
- # off-topic (3)
- # om (70)
- # onyx (17)
- # planck (21)
- # re-frame (3)
- # reagent (2)
- # rum (1)
- # spacemacs (12)
- # spirituality-ethics (9)
- # untangled (44)
- # vim (2)
- # yada (8)
@jumblerg: If I clone hoplon/hoplon master right now, would I get the most compatible version of hoplon for IE 8?
although, i need to look into why the tests are failing more deeply, i'm going to take care of that this afternoon.
the tests may have actually caught something i missed with my minimalist app in firefox
allright good! Thanks!
of course, just ping me when ready!
@micha: sure, i was thinking about stripping ->node, both as a fn and a protocol, from the source altogether based our last convo, given that the string and number cases are no longer necessary
i don't see any problem with how it was, can't we just leave it like that for a while, until we have a reason to change it?
wrt string, number, i thought you were suggesting we didn't need them a few days ago, but i don't recall the particulars, probably misunderstood.
there may be a better way to do it that eliminates that, but it doesn't seem worthwhile at this point
@jumblerg on IE 8 (not 9) I still got a problem
I am on simple
should I check out how to remove devtools on browserstack?
do you see
hoplonKids="[object Object]" yourself?
I don't get this with IE9+
this cause some parts of my pages not to load
the one that depends on castra cells I believe
is this correct:
HEAD is now at 17bd97b... ie-8-proof ->node extensibility, purge hoplon kids atom in body on page reload
you should see something like
$ git checkout HEAD~ Previous HEAD position was 17bd97b... ie-8-proof ->node extensibility, purge hoplon kids atom in body on page reload HEAD is now at 98adfce... add ie 8 special sauce to -head property
sorry I am not good at git
should I checkout again?
oh ok, I did git checkout origin/head
doing git checkout HEAD~ I see exactly what you printed
no worries, i’m not great at in either. sledgehammer your local hoplon repo via
git reset --hard origin/master
IE 9+ works with this branch
IE 8+ doesn't work. I don't see anything in my page
I know you are fixing stuff
just wanted to let you know
@micha: i switched over to thedavidmeister’s more elaborate test app and started using this for x-browser testing; we’ve been broken on ie 8 for a long time.
most of the commits, including the most recent ones, work on minimal hoplon apps, as well as the apps i’m creating internally, but this thing seems to be catching a number of deficiencies. i’m not sure what the deltas are yet between those apps that pass and the test app, but i’m working to find out.
that’s what i was initially suspicious of. but i created a separate test app using his index.cljs.hl page, and i’m using that for functional tests.
one way to deal with this could be to associate some metadata on each one indicating which browser versions they work with, then warn when they are used
@leontalbot: if you use any html 5 elements in your app, it will break because they’re not supported by ie8 in the first place
Oh i see
Is css 3 still ok ? (can't test right now)
Ok will test tonight
@jumblerg: ie8 should still support those elements, they just have a default implementation
but you should be able to do
body.appendChild(document.createElement("section")) in ie8
or in hoplon in general… when new elements are defined, we could make them appear that way in the dom, could be useful for debugging
make it easier to spot things, doesn’t have any production value though, only useful for debugging maybe