B
BG3
Ok, I've got one to add to the known scroll bar / double
scroll problem, that's nearly as annoying.
Now, when you have selected (say, for copying) some text
on a web page with the mouse, and then use the mouse to
move the scrollbar, the selected text becomes unselected!
Used to be that you could scroll twelve pages down and
back up, and the text would still be "blue".
I know it's related to the 824145 update, and since MS is
supposedly looking into the double scrolling issue,
someone should tell them to fix the problem I described
above as well.
Not a huge issue, granted. But seems I have developed
certain work habits that make use of the old behaviors.
Funny that I never gave it a thought.
Besides, I wouldn't be surprised if the old behavior,
which was to leave the text selected until the user clicks
on the page to move the cursor, is specified in some User
Interface Design Guide published by Microsoft...
It's a shame so many good programmers are out of work
while quality seems to be slipping over in Seattle (or
offshore, I suppose). Maybe MS should use some of its $39
Billion in cash to hire a few senior people who can manage
an incremental release and enhancement project! Granted,
these people might not be as cheap as some of the folks
available, but just maybe there's a reason for that. I've
always believed you get what you pay for, no?
scroll problem, that's nearly as annoying.
Now, when you have selected (say, for copying) some text
on a web page with the mouse, and then use the mouse to
move the scrollbar, the selected text becomes unselected!
Used to be that you could scroll twelve pages down and
back up, and the text would still be "blue".
I know it's related to the 824145 update, and since MS is
supposedly looking into the double scrolling issue,
someone should tell them to fix the problem I described
above as well.
Not a huge issue, granted. But seems I have developed
certain work habits that make use of the old behaviors.
Funny that I never gave it a thought.
Besides, I wouldn't be surprised if the old behavior,
which was to leave the text selected until the user clicks
on the page to move the cursor, is specified in some User
Interface Design Guide published by Microsoft...
It's a shame so many good programmers are out of work
while quality seems to be slipping over in Seattle (or
offshore, I suppose). Maybe MS should use some of its $39
Billion in cash to hire a few senior people who can manage
an incremental release and enhancement project! Granted,
these people might not be as cheap as some of the folks
available, but just maybe there's a reason for that. I've
always believed you get what you pay for, no?