I am having a problem with FireFox correctly displaying something.
All other browsers display this correctly but the darn FF does not
You can see the problem by going here:
and clicking on the Country drop down selection of USA, Once you do
then via Ajax the user browser will receive the states of the selected
country and will then via Javascript and CSS will write it into the
designated div. This process works all fine in IE, Chrome, etc. but
on FF somehow it just writes the states into the 1st column and ruins
the look of the page.
Can you suggest what to do to correct this FF bug?
Maybe it has something to do with, there are inline styles setting the display status of the td to “block”. Which makes no sense: it’s a table cell. You want it to remain display: table-cell. This might explain why the next td (who is also set to block) is UNDER rather than NEXT to each other.
Other browsers may be ignoring that statement, knowing that td’s have to be table cells?
This is my guess.
Can you suggest what to do to correct this FF bug?
I don’t think it’s fair to call it a bug unless the specs say browsers should ignore non-table display states.
Note this style is not appearing in the CSS sheet but is added to the td itself in the HTML.
This also doesn’t belong in Accessibility. I think it should be in CSS. I’ve hit the orange flag so a mod can move this over there. But, remove the display: block stuff and I think you’ll be happy.
2nd, this problem had to do (possibly) with Ajax, Javascript, CSS or Php.
So given that it (possibly) was from one or more of these areas and had to do with “Accessibility” over all, then I thought best post it here. OTN, you guys need to be less up tight about this message belongs to here and that message belongs to there. You turn many people away from wanting to use this message board since we are never sure you are going to ***** at us for posting the message to the wrong place. Certainly you can be sure that one wants to post the message to the right board, but sometimes it is a subjective judgment call where the message belongs to since one cannot be sure whether it is a X or Y issue. Anyway, it would be nice if you guys weren’t so up tight about it and trust that a typical person, such as myself, is doing his or her BEST as to where is the BEST place to post the message.
you guys need to be less up tight about this message belongs to here and that message belongs to there. You turn many people away from wanting to use this message board since we are never sure you are going to ***** at us for posting the message to the wrong place. Certainly you can be sure that one wants to post the message to the right board, but sometimes it is a subjective judgment call where the message belongs to since one cannot be sure whether it is a X or Y issue. Anyway, it would be nice if you guys weren’t so up tight about it and trust that a typical person, such as myself, is doing his or her BEST as to where is the BEST place to post the message.
Have a good day.
Wow where did all that anger come from?
All Stomme said was this (after trying her best to help):
This also doesn’t belong in Accessibility. I think it should be in CSS. I’ve hit the orange flag so a mod can move this over there.
I don’t see anything admonishing in the above at all but just a note basically saying that the thread would be better received in a more appropriate forum.
Threads are often posted in the wrong forum and we seldom admonish anyone for posting in the wrong place – we just move them to where we think they will get the best help. If members are being berated for ocassionally posting in the wrong place then that would be wrong but I haven’t seen any evidence of this at all.
We get it wrong ourselves sometimes and will have to move the thread to a more appropriate place as the topic unfolds. The reason we move threads is so that duplicate threads are not posted when the OP doesn’t get an answer because they posted in the wrong forum.
I think we are pretty much saying the same thing.
That is:
You can be sure that a regular user of this board like myself is doing his/her BEST to post the message to the right place. But one cannot be certain always as to where the BEST place is and in fact it would be debatable as the best post is for a problem that I posted.
On that note: “Clearly not accessibility then :)”
What is then accessibility but a combination of many things from Php, to CSS, to Javascript, etc. that together make a HTML page and thus give the users their “accessibility” to a Web site. Maybe I am just mistaken as to what the meaning of “accessibility” is!
What is then accessibility but a combination of many things from Php, to CSS, to Javascript, etc. that together make a HTML page and thus give the users their “accessibility” to a Web site. Maybe I am just mistaken as to what the meaning of “accessibility” is!
It’s a common mistake to confuse accessibility with other issues and as I said we don’t mind if you post in the wrong forum but the chances are that you will getter better replies in the correct forum. Although I do realise that sometimes it is hard to make a choice.
For example I look in the CSS forum hundreds of times a day but don’t venture into the accessibility forum so regularly and would miss any specific css related questions and so a post requiring some css fixes would be better off in the css forum and would get more support there.
Most coding issues aren’t accessibility related although they may have an impact on accessibility. For example if you were coding “skip links” and ran into a bug then although skip links are an accessibility benefit the underlying code is html and css so any buggy behaviour would be solved in the html or css forum first. On the other hand a discussion about whether skip links are good or bad is an accessibility question and would be discussed in that forum.
Nonetheless members should never be worried about posting in the wrong forum as its our job to try and guide them into the correct forum. If anyone is being heavy handed about this then send them to see me
