I need confirmation that this bug report was received by FileMaker, Inc.
Thank you for posting.
I was able to replicate the behavior in your file. I submitted this issue to Development and Testing. I'd like to note if I resize the object by one pixel then size it back the unexpected behavior disappears.
I'd like to know how you created the object. Could you provide the steps to reproduce in a new sample file?
Don't know if it's drop box or firefox, but I can't download the file. It opens, but as text and I can see all kinds of interesting "gobblety gook" instead of a button to download the file as is usual for drop box.
Try the link again now.
Don't have to. I had already copied and pasted the link to a URL field and appended that text myself in order to download the file and examine it. My main concern is that I use drop box and haven't encountered that issue with FMP files, but have with other file types such as movie files.
Double clicking it while in layout mode, BTW, caused the size of the button to almost disappear a small vertical fraction of the original still remained.
TSGal, I don't remember how that button was created. It might have been a button that was converted from FM11 to FM12.
It doesn't look like an FM11 button. The features it has--including a gradient, don't match what I'd expect from an earlier version.
On the other hand there is a known limitation, can't get Filemaker to call it a bug, where editing the text format of a button from a converted file spontaneously resizes it to just bigger than the text label in the button. Since this button doesn't have any label text, that might explain the sudden size change down to nearly nothing.
Time for a few tests...
I can reproduce it in this fashion:
Create a file in FMP 11. Put a button on it with no label text.
Convert file to Fmp 12.
I'd guess that this issue is related to this one: Buttons spontaneously change size and position when a text style is applied
This is one of many acknowledged bugs that can be found in the Known Bug List thread here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: https://www.dropbox.com/s/jt09b82i0xijbu3/FMP%20Bugs.zip
This is one of the few cases where I disagree with FileMaker. They've told me this is not a bug and point me to a knowledgeBase article that documents this issue. To me, it acts like a bug and thus needs to be reported as such so that others can find it when they search for known bugs.
In my book, the programmers that wrote the conversion code didn't write the conversion code as they should have to fully convert the button objects during the file conversion.
Thank you for taking the time to find the key to reproducing this issue. I have updated my orignal report to Development and Testing with the steps to reproduce.