Request #48815
From:
Account Type:
Free Account
Dreamwidth:
Account Name: ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
ari_soleil
ari_soleil
Email confirmed?
Yes
data version: 10
scheme:
tropo-purple
Time posted:
Tue, 23 Apr 2024 22:50:12 GMT (54 weeks ago)
Status:
answered (still needs help)
Summary:
bizarre issue where only a small amount of hex codes display wrong?
Original Request:
I just made this dw account a day or two ago, and I'm trying to style it. So while my issue is somewhat like the "html doesn't work" thing, it also seems to be somewhat different. For only one div in my html code, hexadecimal is broken, in that blue is not recognized. So if you type #f66 or #f69, what you get is orange, as though you typed #f60. If you type #777 through grey to #aaa, what you get is moss green, as though you'd typed #770 through #aa0. It's so odd. The whole rest of the entry I'm coding, isn't having the hexadecimal colors fluke out like this; just the one div.
Additionally, I uploaded some pictures, decided I liked them in different angles and sizes, deleted them and re-uploaded... but my file size limit only kept increasing. So do I take segments towards image limit, for every pic ever uploaded, even the ones I delete, or is that a glitch too?
Diagnostics: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.110 Safari/537.36 Vivaldi/2.7.1628.30
Additionally, I uploaded some pictures, decided I liked them in different angles and sizes, deleted them and re-uploaded... but my file size limit only kept increasing. So do I take segments towards image limit, for every pic ever uploaded, even the ones I delete, or is that a glitch too?
Diagnostics: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.110 Safari/537.36 Vivaldi/2.7.1628.30
A second div in the entry started fluking out the same way. Currently, I asked for the text to be white, so it's yellow. I guess the earlier-rendered divs don't have the problem, but the ones rendered after a certain point in time, are off. Oddly enough, black still seems to work, but I suppose that's because blue is stuck at zero.
While coding my page isn't the most important thing in the world, I would like to be able to see what I typed, better.
While coding my page isn't the most important thing in the world, I would like to be able to see what I typed, better.
Hi there!
I apologize for the delay in replying to your message. I did mention it to the development team and they were at a bit of a loss.
Have you tried expressing the color code as six digits instead of three? For example, #ff6699 instead of #f69.
Let us know if that makes a difference!
Best,
--Jen
I apologize for the delay in replying to your message. I did mention it to the development team and they were at a bit of a loss.
Have you tried expressing the color code as six digits instead of three? For example, #ff6699 instead of #f69.
Let us know if that makes a difference!
Best,
--Jen
I have tried that, yes. At first I asked around online for an answer to this problem, and according to multiple html4 and html5 help websites, trying to tell text to wrap on certain css's causes odd issues with the display, sometimes resulting in color changes and sometimes resulting in spacing changes. But the problem exists, even for my div's that I didn't tell text to wrap on. ^^;;;
Thank you for getting back to me so quickly, and there's no need to apologize for the delay; I know you must have a lot of customers and my issue isn't really pressing or anything. I'm sorry for the coding annoyance. I know how difficult it can be, to figure out which coding phrase is causing the issue, and certainly this is the first time I've ever come across this problem, myself.
If you'd like to recreate the problem, to see it yourself, if I type a div like (less than sign goes here) div style="float: left; background-image:url(url of a picture goes here); background-size: cover; width:400px;"(more than sign goes here) (less than sign goes here)font color="#ffffff;"(more than sign goes here) (less than sign goes here)b(more than sign goes here)
and then I put text in it and type /div /font /b with corresponding "more than and less than signs" around them, then the white text comes out yellow. And if I change the hexadecimal code for the font color to #fff, it doesn't make it white; it's still yellow. (and yes, the parentheses around the url are the way I typed that, but the parentheses showing where the more or less than signs are, only show what the html would look like, because this page warns that any html will actually be rendered, not seen. ^^;;;;;;
Thank you for getting back to me so quickly, and there's no need to apologize for the delay; I know you must have a lot of customers and my issue isn't really pressing or anything. I'm sorry for the coding annoyance. I know how difficult it can be, to figure out which coding phrase is causing the issue, and certainly this is the first time I've ever come across this problem, myself.
If you'd like to recreate the problem, to see it yourself, if I type a div like (less than sign goes here) div style="float: left; background-image:url(url of a picture goes here); background-size: cover; width:400px;"(more than sign goes here) (less than sign goes here)font color="#ffffff;"(more than sign goes here) (less than sign goes here)b(more than sign goes here)
and then I put text in it and type /div /font /b with corresponding "more than and less than signs" around them, then the white text comes out yellow. And if I change the hexadecimal code for the font color to #fff, it doesn't make it white; it's still yellow. (and yes, the parentheses around the url are the way I typed that, but the parentheses showing where the more or less than signs are, only show what the html would look like, because this page warns that any html will actually be rendered, not seen. ^^;;;;;;
Hi there -
Part of the issue is that the closing tags are in the wrong order. They should close in the opposite direction they were opened so close: /b, then /font, then /div.
If this doesn't correct the issue, come back and let us know so we can go digging around to figure out what's up.
Grazie,
H2
Part of the issue is that the closing tags are in the wrong order. They should close in the opposite direction they were opened so close: /b, then /font, then /div.
If this doesn't correct the issue, come back and let us know so we can go digging around to figure out what's up.
Grazie,
H2
This didn't fix it.
You must log in to answer Support requests.
Go to: previous open request, next open request
Return to the list of open requests.
Back to the Support Area.