cottage14 opened a new issue #1103: URL: https://github.com/apache/royale-asjs/issues/1103
Gabe Barbosa reports: "https://royale.apache.org/asdoc and I'm using mostly emulation components. This is on the latest chrome browser on desktop and mobile (android). If there's another browser I should be using please let me know. Here's the errors I see all the time. Honestly never checked the console till now, that's on me. From my perspective the docs are what should keep a developer from having to dig into the source code. One should be able to always trust the docs. Right now I don't. Here are my assumptions. Blue properties/methods are implemented Red properties/methods are NOT implemented Green properties/methods added specifically for Royale? An example: mx:UIComponent the docs show the public function of "invalidateParentSizeAndDisplayList()" as blue which I'm assuming means implemented. When I dig into the source code I see that this is actually a protected function and a trace indicating this is not implemented. CONSOLE: https://royale.apache.org/asdoc/#!mx.controls.advancedDataGridClasses/AdvancedDataGridColumn Mixed Content: The page at 'https://royale.apache.org/asdoc/' was loaded over HTTPS, but requested an insecure stylesheet ' http://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css'. This request has been blocked; the content must be served over HTTPS. ASDoc.js:94 Mixed Content: The page at 'https://royale.apache.org/asdoc/' was loaded over HTTPS, but requested an insecure element ' http://royale.codeoscopic.com/wp-content/uploads/2017/10/page-bg-1-1920x300.png'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html G.fc @ ASDoc.js:94 (index):1 Mixed Content: The page at 'https://royale.apache.org/asdoc/' was loaded over HTTPS, but requested an insecure element ' http://royale.codeoscopic.com/wp-content/uploads/2018/01/apache-royale-tm-logo-light.svg'. This request was automatically upgraded to HTTPS, For more information see https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html ASDoc.js:60 Uncaught SyntaxError: Unexpected token t in JSON at position 8140 at JSON.parse (<anonymous>) at uo.parse (ASDoc.js:392) at Kn.G.ed (ASDoc.js:320) at Hj (ASDoc.js:56) at Gj (ASDoc.js:57) at dp.G.dispatchEvent (ASDoc.js:55) at dp.J.dispatchEvent (ASDoc.js:60) at dp.Yn.dispatchEvent (ASDoc.js:353) at dp.G.Ln (ASDoc.js:471) (index):1 Mixed Content: The page at ' https://royale.apache.org/asdoc/#!mx.controls.advancedDataGridClasses/AdvancedDataGridColumn' was loaded over HTTPS, but requested an insecure stylesheet ' http://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css'. This request has been blocked; the content must be served over HTTPS. === @aharui writes, "I don’t remember how the content gets to https://royale.apache.org/asdoc There is/was a Jenkins job that builds asdoc with every change (ASDoc is a Royale app!). But if committers commit code with broken ASDoc then that will break the build and ruin ASDoc if it is somehow getting published to or redirected from that url. Also, the CI hosting Jenkins goes down on occasion as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
