Gnizmo said:
there is nothing defensive about calling someone ignorant when they don't know what you are talking about. I am not jumping on you for calling for a fix that I have championed before. I am jumping on you for talking out of your ass needlessly. It is not a quick fix. It is apparently a fairly complicated problem that has no easy solution. If you want to complain about a problem go ahead. I will help you with this one and try to work and find the root cause of it all. Your over the top ignorant claims that it is an easy quick fix annoy the shit out of me though. I can't stand it when people talk about stuff in an authoritative maner when they don't know what they are talking about. I will try to dig up the thread where it was initially addressed but it won't tell you much. I, and others, got PM responses from ioi at the time. The basic response I got was he didn't know how to fix it. From what I gather he doesn't even know how this error could happen. It is very odd that this is an Opera specfic bug that occasionally people claim does not affect them. |
Read what you wrote--that *is* defensive (we can argue semantics all night, though, if you like).
But let's just clarify this further: just because the person that's tackling the problem can't fix it doesn't mean it isn't an easy fix. I don't know about you, but I've made several mistakes in the past that have been *Mickey Mouse* errors that I hadn't picked up on because I was too close to the project (I call these 'face-palm' or 'd'oh' moments). When someone else not so aborbed in the nuts and bolts went over it, voila!, the error was discovered in less time than it took for me to compose this post (even though I'd been staring at it for hours). The point is, you're getting worked up (and, yes, defensive) at a harmless comment. Hell, you've said a lot worse than I have since this exchange began and I'm still not personally insulting you. Would you prefer I said you were over-reacting? Would that make it more acceptable?
Following on from those face-palm moments: I've run across similar, browser-specific, problems in the past and they've been remedied with little fuss (and, a few times, with the Admin/DB guy/MS guy, etc. doing the face-palm). In all those cases, the fixes have been "Mickey Mouse" or, if you prefer, "simple", "easy", or "painless".
Also, if it had already been addressed, would it have been so hard to say: "hey, look, it's been noted and we've attempted to deal with it to no avail. Maybe you could offer some insight on this and, if not, you're out of luck." Would that have been so difficult?
Note: if the Admin wants an outside party to look at the code and see if another set of eyes could ferret out the problem, that is a reasonable solution. However, I made the assumption that the Admin would not want to open up the guts of his site to the tinkering of a 3rd party he doesn't know--I know I'd have reservations against doing so myself which is why I didn't go "hey, how about you let me, some random guy on the net, go swimming in the entrails of your site to see what's up".
Anyway, I'll leave it be at this (you may continue this but it will be a monologue from this point forward). If someone actually *does* want some help, I'm more than willing to lend a hand (hell, I might do it anyway--could be something odd with Opera that doesn't actually require anyone looking at anything proprietary at all).







