Skip to content

If an image is taking longer to download than usual, then the "could not extract height/width" error was being displayed. It couldn't be extracted because the image wasn't done downloading yet.#213

Open
mweichert wants to merge 1 commit intoGalleriaJS:masterfrom
mweichert:master

Conversation

@mweichert
Copy link
Copy Markdown

Fixed 'could not extract height/width of image' issue, if the image is taking longer than 2 seconds to download

…s taking longer than 2 seconds to download
@anandkkpr
Copy link
Copy Markdown

EDIT:

Moved my comments about Michael's update and code revisions to a new pull request - the reference is below...

@janpub
Copy link
Copy Markdown
Contributor

janpub commented Nov 14, 2011

None of above fixes the problem. I am still getting "could not extract width..." error on Chrome (IE and FF works fine).

anandkkpr added a commit to anandkkpr/galleria that referenced this pull request Dec 3, 2011
Quote:
"If an image is taking longer to download than usual, then the "could not extract height/width" error was being displayed. It couldn't be extracted because the image wasn't done downloading yet."

I've added a comment into that issue's thread and would've wanted to update Michael's code itself but was unable to find out how to do so - I'm a noobie to GitHub... So please forgive me if I'm doing this the wrong way and point me in the right direction if you know how to modify a user-submitted "pull request".

I've commented the code as best as I know how and if you wish to see the full reasoning for why I'm submitting this, please visit the original issue:

GalleriaJS#213 (comment)

Many thanks for your kind patience!

Best regards,

Anand
@ergophobe
Copy link
Copy Markdown

I just tried 1.2.7a2 and this problem is still not resolved.

It seems that any time a max-width property is set, I get these errors. This "flavor" of the issue is the same one that I'm having:

http://drupal.org/node/1402952

@marcenuc
Copy link
Copy Markdown

Can you try the patch proposed in #214 with the fix given in the following comment #214 (comment) ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants