[Eug Wanker]

I often run into a problem where cutting and pasting stuff off a page in Safari gives me unwanted spaces. I recently ran into this again when posting my thread about PCI incompatibilities on the G5.

Text:
The G5's PCI slots accomodate 3.3 volt-powered PCI cards only, compared to the G4's PCI slots which supported mixed voltage cards (5.0 V, 12 V, or 3.3 V). While some of Digidesign's PCI cards are compatible with both 5.0 V or 3.3 V PCI slots, others require 5.0 V-capable PCI slots and will be physically incompatible with Apple's new Power Mac G5.

Safari:

Code:
compared          to the G4's PCI slots which supported mixed voltage cards (5.0 V, 12 V,          or 3.3 V).

Camino:

Code:
compared to the G4's PCI slots which supported mixed voltage cards (5.0 V, 12 V, or 3.3 V).

P.S. If you want to post about the PCI slot incompatibilities, please do so in the other thread devoted to it.

[Jan Van Boghout]

Hyatt mentioned something about having fixed a bug that causes text selection to actually apply to the source beneath it. So you're probably not selecting the visible text in this case, but the underlying html text.

[Eug Wanker]

Originally posted by Jan Van Boghout:
Hyatt mentioned something about having fixed a bug that causes text selection to actually apply to the source beneath it. So you're probably not selecting the visible text in this case, but the underlying html text.

Yes, you are correct, thanks.

Code:
      <p>The G5's PCI slots accomodate 3.3 volt-powered PCI cards only, compared 
        to the G4's PCI slots which supported mixed voltage cards (5.0 V, 12 V, 
        or 3.3 V). While some of Digidesign's PCI cards are compatible with both 
        5.0 V or 3.3 V PCI slots, others require 5.0 V-capable PCI slots and will 
        be physically incompatible with Apple's new Power Mac G5. </p>

It seems to be including the extra space used for formatting the underlying code. So I guess the new builds don't have this issue?

[Jan Van Boghout]

Originally posted by Eug Wanker:
It seems to be including the extra space used for formatting the underlying code. So I guess the new builds don't have this issue?

I thought it was fixed in Panther, so I assume it will be fixed in future Jaguar builds as well.