I think it just the way it is designed.
If you have font size > 100% it will show under Transform before selecting.
The true value (kind of achorpoint) is the centre of the text/object and relative to the left top corner.
Is it possible you have an "empty" text box over the one you can see, and you selected that one first by mistake?
No this is not possible. I have recreated this scenario with over a dozen title pages within various APP CS5 projects. I even verified my "issue" by creating a new title page and adding a new text box within the title page. After placing the title page in my sequence, I was able to see the same "problem."
It is not clear to me what the design purpose would be for the properties of a title element not to show the actual properties, so I indulged my curiosity and played a bit.
I tested in CS4 (and then CS3), and observed what I think are the same issues. I think I would call this a "bug," although one whose effects are easily worked around.
Create a title. Type a text box (or any other object, such as a shape). The x pos, y pos, width, and height are all "accurate." Close and reopen (you do not have to put the title in a sequence).
I find that the text box (and the first text box if more than one is created) is selected by default, but the properties are Angela's "wrong" ones: 100, 100, 100, 100. Click in another text box or shape etc (and it doesn't matter with what tool), the properties are then "correct."
Is the 100 x 4 a default for something? (I don't see any such defaults.) Is the titler selecting an object by design (I don't think I prefer that, but I can see that being a design choice), but incorrectly failing to set the properties to the object selected? But then why put the 100 x 4?
I also ran the test in CS3; same thing.
I'm not bothered by it, but I do think it is a bug, so I filed a bug report. You can only pick one PR version to report, and since I do not have CS5 installed yet, I reported it for CS4 (and said I have demonstrated it for CS3 and CS4 and that a forum user reported it for CS5). Angela, you may also wish to report it so there is at least one report for CS5.
One is enough
Angela, you may also wish to report it so there is at least one report for CS5.
CS4 shows exactly the same 'problem' that's why i did not file a bug report.
Ha, ha! Thanks for that clarification. It was so much fun, I was starting to react like potato chips: can't post just one....
For those of you who have not filed bug reports (or feature requests), I know bug reports are taken seriously and thoughtfully. Not all bug reports get responses, but on some, I have gotten questions. And in support of Jeremie's point, it only takes one flag for a significant bug to get on the list.
Feature requests: the more people requesting the better.
Thanks so much for testing this with CS3 and CS4 and reporting the bug. I can at least be comforted by the fact that I am not crazy (at least concerning this issue!).
Jeremie, it sounds like you are saying that there is no need for this bug to be reported against CS5 since Stan has already reported it for CS4, correct? If I need to right a bug, let me know. I've worked many years as a telecom engineer and have written my share of software problem reports.
Stan mentioned CS5 in the bug report, too, so another bug is probably not necessary.