Quote:
Originally Posted by Hitch
I'm obviously missing something. I don't understand why you have two different files? And why wouldn't the files have identical KF7 markup? Can you please elaborate?
|
Sorry; I made two different files with two different sizes of image. I was trying to see if the size of the image
file would have any bearing on how big it was displayed on the screen. So I saw that the same markup was produced no matter the size of your image--a logical conclusion, but whatevs.
Quote:
Originally Posted by Hitch
Yes, I have a bunch. I wonder if we are somehow miscommunicating, or if I'm misunderstanding your intent? I hope you don't mind my questions, to obtain some clarity:
- Why are the images inside a header? H1, to be precise? I noticed this, I think, earlier, but thought it was anomalous, but here I see it again? Why is this?
- You have a bunch of mixed instructions here. I see a height instruction of 9%--which is for what? Is that intended to be for the image, or for the heading, that's containing the image?
- Then there's a font size of "3," which is typical KF7 sizing.
- My inference is that the heading is being used to constrain the image size. That's what I see--just like using divs to constrain images for iBooks, essentially.
- The % shouldn't work at all, for this. That should affect the view on a KF8 device, not a KF7, assuming that it's interpreted to be for the heading.
|
Questions are good; clarity is good
- The images are inside a header because that's the markup that InDesign generated. No more, no less.
- Sorry, I was confused earlier and thought that the 9% was on the image, but you're right, it's on the header tag. That was what InDesign generated; I don't know what purpose there is for putting a % height setting on a header.
- Font size 3, sure. Again, ID-generated.
- Mayhaps. Again, not intended that way, but maybe that's what's happening. (I am familiar with the iBooks image problem and the workaround.)
- Interesting, okay. So basically the sizing settings on the header, a % and a zero, aren't doing anything, based on what we know of KF7.
Quote:
Originally Posted by Hitch
What I've been saying is that you either write something like this:
Code:
<img class="90" src="yadda.jpg" height="50" width="XXX">
With the Class defined as being 90% (width or height, your call), or whatever it is you want for that image, in the CSS,
OR, you put the style inline, inside the img tag. Either will make the image work correctly in both KF8 and KF7, but you need to have both. Otherwise, the KF7 simply won't work. |
I'm tracking that you would use a class with a % sizing, and that will bear out in the KF8 file. I do have that, and in the KF8 file they are percentage-sized. (I didn't attach pictures of that--it's just the DX Previewer, so just KF7 was shown.)
The part that wasn't working for me was the inline sizing on the img tag. I haven't included any markup examples, but the reason I started this thread was that even setting the width="xx" and height="xx" on the img tag didn't seem to be affecting its size in the KF7 file, at least on my K1 (and the DX Previewer).
Quote:
Originally Posted by Hitch
If you try plain old image coding, without putting the image inside a heading, without putting it inside font tags, without putting it inside a paragraph tag, I think you'll see what I mean. You're getting artificial results, more or less, because your images are being put inside other elements, that wouldn't normally hold them, like headings or font tags. You know what I mean?
(You can use Divs to provide constraint for an image, but AGAIN, you still need the KF7 coding for the KF7 devices).
Right?
Hitch
|
The datum you've given me is that, unless you specify a width and height
on the img tag itself, it will blow up to 100% of the screen size.
What I'm seeing is that the image is simply being displayed on the screen in the size of the file,
regardless of any width or height attributes on the img tag. As you can see from my screenshots, I made 2 files with different sizes of image, with the image sizes painted in the image itself for clarity. And you can see from the screenshots that they're displaying at two different sizes in the DX Previewer.
(It's just different behavior from what you were saying, hence all this.
)
So then, you're theorizing that this behavior is because the img tag is within an h1 tag. As we've gone over, the h1 tag isn't even really constrained to any particular size, since the size attributes on it aren't supposed to be applicable to KF7. So the idea is that by simply putting an img tag inside another tag, you can prevent it from expanding to 100% of the screen size...right? (Similar to the ibooks bug, except you don't have to do the 100% width/height on the img, and the explicit size settings on the constraining div/span.)
If that's true, then there's two ways to constrain image sizes on KF7. Remove the img tag from everything and put sizes on it, or stick it in another tag. That would be the conclusion, just two ways to go about it. Next time I'm at my desk I'll pull the sucker out of the h1 tags and see how it looks. Based on what you're saying, it'll explode up to 100% screen size.
Anyway, I hope that I've clarifies? In the end, it just may be that we accidentally found another way to counter a sizing bug on KF7.