This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (14)
- # architecture (1)
- # beginners (21)
- # boot (301)
- # clojure (93)
- # clojure-brasil (56)
- # clojure-india (4)
- # clojure-italy (11)
- # clojure-japan (25)
- # clojure-russia (16)
- # clojure-sg (1)
- # clojure-uk (5)
- # clojurescript (64)
- # clojurex (4)
- # clojutre (7)
- # cursive (18)
- # datascript (35)
- # datomic (212)
- # editors (27)
- # emacs (38)
- # events (9)
- # funcool (21)
- # hoplon (105)
- # jobs (2)
- # ldnclj (41)
- # ldnproclodo (4)
- # liberator (89)
- # luminus (5)
- # off-topic (32)
- # om (39)
- # onyx (1)
- # re-frame (9)
- # reactive (1)
- # reagent (34)
- # testing (42)
- # yada (4)
or maybe a boot task that inlines all styles? i guess that would make the page bigger and defeat caching
which is why we might even see the prerendered page for awhile but then hoplon kicks in and kills it and gradually rebuilds it
that bakes in the CSS to present a nice loading page, which is SEO-able markup underneath
i don't know how much difference the inline vs stylesheet styles make, what's the benefit there?
i see. so daniel's fix reduces but does not eliminate the amount of unstyled time?
so if i have that display:none in the head and a
(body :style (cell "display: block") ...) the flashing disappears indeed
ah, for the subpages of our app which normally appear when u click a menu item are all :style "display:none" with a :toggle which depends on the route-cell
the previous hack is obviously not nice, because it assumes u want the body to be block, but your css frameworks might set it to flex for example..
A friend of mine wants to create a discourse instance for the broader Clojure community, providing categories/mailing lists for individual projects. You have your setup already but if it causes extra work might be worth considering. He's @plexus
@martinklepsch: thanks! yes i saw that. although i think it's probably best to leave ours where it is, we have a lot of content on it
@alandipert: maybe a good time to send some sticker resupplies to Juho or me :stuck_out_tongue:
@alandipert: thanks for the mentions in your announcement! we could also make some use of some more stickers. the team likes your ecosystem a lot and they are proud to be able to use it at work (at least that's what i sense :simple_smile:
does anyone know how i can get the stack trace associated with an error in the js console in firefox?
i feel like bisecting my application to see where an error originates must be the wrong way to do it
Stack traces Just call console.trace() and Firebug will write a very informative stack trace to the console. Not only will it tell you which functions are on the stack, but it will include the value of each argument that was passed to each function. You can click the functions or objects to inspect them further.
let me know if you found solution :wink: we also should check on more browsers then just chrome haha :smile:
e = Error("asd"); e.stack "Error: asd at Error (native) at <anonymous>:2:5 at Object.InjectedScript._evaluateOn (<anonymous>:905:140) at Object.InjectedScript._evaluateAndWrap (<anonymous>:838:34) at Object.InjectedScript.evaluate (<anonymous>:694:21)"