This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-05-18
Channels
- # announcements (11)
- # architecture (1)
- # aws (2)
- # beginners (101)
- # calva (3)
- # clj-kondo (2)
- # cljdoc (1)
- # cljs-dev (20)
- # clojure (92)
- # clojure-dev (34)
- # clojure-france (1)
- # clojure-italy (2)
- # clojure-spec (13)
- # clojure-uk (3)
- # clojurescript (28)
- # cursive (7)
- # data-science (58)
- # datomic (18)
- # docs (1)
- # fulcro (11)
- # graphql (3)
- # hoplon (25)
- # klipse (3)
- # leiningen (4)
- # nrepl (3)
- # off-topic (57)
- # pedestal (1)
- # portland-or (1)
- # precept (1)
- # reagent (5)
- # reitit (2)
- # rewrite-clj (4)
- # ring (1)
- # shadow-cljs (97)
- # sql (90)
- # tools-deps (2)
While developing a chrome extension, is it possible to have fulcro-inspect interact with the options page ?
I see Installing Fulcro Inspect {}
in the console and __fulcro-inspect-remote-installed__="true"
on my html element, yet the fulcro-inspect popup says Fulcro app not detected
.
I suspect chrome prevents injections from other extensions.
Is there some special content_security_policy that would help or should i just do without fulcro-inspect in this particular case ?
@U066U8JQJ would know most about that
@U13RRNF2M yeah, that doesn't work, I never did a debug on why, but I suspect too of some security policy
there is an idea to have a fulcro inspect stand alone, most of the architecture can support that, but never got the time to work on that, that could enable reach from anywhere (including chrome extensions)
the react people are using an external tool for this, and it looks like there is an electron based thing in fulcro-inspect too,
yeah, exactly that, they just have more people to work on it, hehe