From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (mailfrom) identity=mailfrom; client-ip=8.23.224.61; helo=out.smtp-auth.no-ip.com; envelope-from=kevin@carhart.net; receiver= Received: from out.smtp-auth.no-ip.com (smtp-auth.no-ip.com [8.23.224.61]) by hurricane.the-brannons.com (Postfix) with ESMTPS id C490F779A3 for ; Sun, 10 Dec 2017 02:00:21 -0800 (PST) X-No-IP: carhart.net@noip-smtp X-Report-Spam-To: abuse@no-ip.com Received: from carhart.net (unknown [99.52.200.227]) (Authenticated sender: carhart.net@noip-smtp) by smtp-auth.no-ip.com (Postfix) with ESMTPA id 6A7C43C7 for ; Sun, 10 Dec 2017 02:02:27 -0800 (PST) Received: from carhart.net (localhost [127.0.0.1]) by carhart.net (8.13.8/8.13.8) with ESMTP id vBAA2QEI029448 for ; Sun, 10 Dec 2017 02:02:26 -0800 Received: from localhost (kevin@localhost) by carhart.net (8.13.8/8.13.8/Submit) with ESMTP id vBAA2QEu029445 for ; Sun, 10 Dec 2017 02:02:26 -0800 Date: Sun, 10 Dec 2017 02:02:25 -0800 (PST) From: Kevin Carhart To: edbrowse-dev@lists.the-brannons.com Message-ID: User-Agent: Alpine 2.03 (LRH 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: [Edbrowse-dev] document.head.querySelector X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.24 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Dec 2017 10:00:21 -0000 Sorry to write about multiple things concurrently, but I also hit this in the xqsuperschool code. Interesting.. it's expecting document.head.querySelector so that it can query for metas by selector syntax. I don't know why it needs to be called on document.head, when metas by definition will only be in head. getConfig: function(name) { var element; element = document.head.querySelector("meta[name='action-cable-" + name + "']"); return element != null ? element.getAttribute("content") : void 0; }, I have been banging my brains on it for a while. Is there a proper place to add functions to document.head? I tried adding it at the very bottom, after document.querySelector, and it wasn't recognizing document.head unless I am misinterpreting messages. Does this need to take place after third.js has run? No.. it doesn't, right? Otherwise you wouldn't be able to define document.querySelector either. thanks Kevin