New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 716933 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 640844



Sign in to add a comment

Onlyarg.com "A parser-blocking error" in console. Images don't charge, it only appears the link.

Reported by javiersc...@gmail.com, Apr 30 2017

Issue description

<b>Chrome Version       : <Copy from: 'about:version'></b>
URLs (if applicable) : www.onlyarg.com
Other browsers tested: Mozilla Firefox
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
         IE:

What steps will reproduce the problem?
(1)Loading the page
(2)Just watching a post, when there is a picture in it, I can't see it, I only see it's link.
(3)

What is the expected result?

To see the picture instead of the link

What happens instead?
I see the link of the picture, like this "[img=www.example.example]" instead of the picture

Please provide any additional information below. Attach a screenshot if
possible.

https://i.gyazo.com/7b85ff3dc04eb0dbfcdaa4f2a00fc354.png

 
Chrome version: 	58.0.3029.81 (Build oficial) (64 bits)

Comment 2 by kochi@chromium.org, May 1 2017

Labels: Needs-Feedback
I don't understand Spanish, so I am not sure what the screen shot says,
but are [Imagen: https://i.imgur.com/3yBPYQt.png] and [Imagen: http://k37.kn3.net/8EBFEA0A0.jpg] is what you are reporting?

Could you check if this is working for your firefox, and include what environment
you are using them (desktop windows 10, etc.)?

Also, could you copy and paste the verbose error message you are seeing
in the developer console here? It is very helpful to understand what went
wrong.

Status: WontFix (was: Unconfirmed)
I turned on chrome://flags#disallow-doc-written-script-loads but don't see anything actually getting blocked (see https://developers.google.com/web/updates/2016/08/removing-document-write).  So I cannot reproduce this either.  Possibly just a site bug.  Closing due to lack of response.

Sign in to add a comment