- From: David Earl <david@frankieandshadow.com>
- Date: Tue, 26 Jul 2016 12:57:52 +0000
- To: Denis Ah-Kang <denis@w3.org>, site-comments@w3.org
- Message-Id: <CANt01SR6suCP68FugGWinGRprRjAfLOFpUzPuGrHvkL=+BO+dQ@mail.gmail.com>
Many thanks, I've done that. David On Tue, 26 Jul 2016 at 05:49 Denis Ah-Kang <denis@w3.org <mailto:denis@w3.org>> wrote: Hi David, Although there are not many contributors, that project is developed on Github [1]. May I suggest you create an issue and the maintainer should get back to you. Regarding the feedback link, I submitted a pull request to point users to Github [2]. Regards, Denis [1] https://github.com/w3c/link-checker <https://github.com/w3c/link-checker> [2] https://github.com/w3c/link-checker/pull/6 <https://github.com/w3c/link-checker/pull/6> On 07/23/2016 12:38 AM, David Earl wrote: > Hello, > > Since pretty much all browsers block http embedding in https pages, can > I suggest that the W3C link checker could usefully check this condition. > (Of course if the source is not via a URL, you'd have to have a check > box or some such indicating the source is intended to be served over > https, but in the normal case where someone is checking a remote site, > you'd already know this). I'm talking about <img src='http://...'>, > <video src='http://...'> and related, <iframe src='http://...'> etc. > > (By the way, the feedback link at the bottom of the link checker page at > https://validator.w3.org/checklink <https://validator.w3.org/checklink> doesn't seem to do anything useful, > or I would have used that). > > Just a thought, > David Earl >
Received on Tuesday, 26 July 2016 15:38:49 UTC