The Web Design Group

... Making the Web accessible to all.

Welcome Guest ( Log In | Register )

> has there been a change in the way Chrome renders images in html ?
koffeeman
post Sep 22 2019, 12:37 PM
Post #1


Newbie
*

Group: Members
Posts: 12
Joined: 17-September 19
Member No.: 26,991



the rendering of images in chrome has changed on my web pages.

i have web pages that display any number of images (and thumbnail images) on an html web page.

before: images would display until the rightmost edge of the screen or browser window was reached and continue on the "next line" making all images viewable (at least until the bottom of the screen or window is reached)

now: images continue to display on "one line" and a scroll bar is added to scroll the page to the images off screen/off window.

i have attached a zip file with directories and html and jpg & gif files

am i allowed to say that Edge still displays (as of today) the pages as i intended

Chrome *USED* to work this way up to about early September (that is: render as many images and wrap around to the next line as required). in my example change from full screen to a smaller browser window.

Has some html spec changed for rendering images ? Will Edge (and all other browsers) work this way in the future?
- or is this a bug ?
i have tried many other"max-width" type tags to no effect.

if this IS the correct action now, can someone help me with "what to add/what to do" to get it to work and display as many images it can (on multiple lines) regardless of screen width (1377, 1280, etc) or window width ?

thank you (and please tell me if i have included this question in the wrong section)
User is offlinePM
Go to the top of the page
Toggle Multi-post QuotingQuote Post
 
Reply to this topicStart new topic
Replies
koffeeman
post Sep 23 2019, 12:58 AM
Post #2


Newbie
*

Group: Members
Posts: 12
Joined: 17-September 19
Member No.: 26,991



thank you, thank you, thank you.

changing the   to a space fixed the image wrap around.

secondly, having the &nbsp; beside the image and part of the trigger to link to the next html was in the specs, client wanted the jump even if the user clicked on the space between images. but he only wanted one space, therefore the "<a" for the next link was at the end of the line. puting each <a ...></a> on a separate line generated more space than he wanted between images.

with your suggestions i will be changing the html being generated to ONE line of:

<a href="file.html"><img src="file.jpg" width="x" border="2" title="x" alt="x"></a>

this looks better, easier to code in the html generator program, and WORKS as intended - if the client insists on using the space as part of the link, i guess i'll have to tell him to get new users who know how to click on the image (i wonder how that will go over Monday morning)

again, thank you very much for your help.
User is offlinePM
Go to the top of the page
Toggle Multi-post QuotingQuote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



- Lo-Fi Version Time is now: 6th December 2019 - 11:10 AM