Bug report - hidden confirmation buttons in HDR on 13" display

For the HDR Pro function, hidden buttons 'OK' and 'Cancel' on Macbook Pro 13" running Snow Leopard and Photoshop CS5.
Of course I can use the 'esc' key for 'Cancel' and 'return' key for 'OK' - but this is still annoying.
See image below to illustrate this:

My display resolution is 1280x800 (like any 13.3" makbooks by apple) so it should have been fine - the image attached has the window magnified to full screen (on Mac, that means between the dock and the upper status bar). On a 1600x1200 external display the buttons show up fine.
I also tried playing a bit with the window while hiding the dock, and got interesting results:
If the dock is hidden when I launch the "Merge to HDR...", the 'Cancel' and 'OK' buttons are showing up fine. Then, I can un-hide the dock and they would still appear fine within the scaled down window
If the dock is not hidden when I launch the "Merge to HDR...", the buttons are missing. If I hide the dock at this stage the buttons would still be missing (showing only about one pixel of the top of those buttons).
So, maybe the dock takes just enough pixels to reduce the overall available screen resolution to less than 768, but I believe this is a bug - especially since those computers with that resolution (i.e. 13.3" Macbooks running MacOSX) are widely in use and considered pro, I think it should be supported without such glitches.
Thanks,

Similar Messages

Bug report - apex.confirm

Apex 4.0.2
See http://apex.oracle.com/pls/apex/f?p=24317:79
Both regions have a button that submits the page with the following URL javascript:apex.confirm('Are you sure?',{request:'FOO',showWait:true});The one at the top of the page works fine. But if you scroll all the way to the bottom of the page and click the Submit button, the confirm dialog is shown fine. But the ShowWait indicator and the gray modal/page overlay are not visible, the probably assume that the entire page is visible with no vertical/horizontal scrolling.
Can it be made smarter to show the showWait indicator and overlay on the current page viewport?
Thanks

Override the position property of the apex_wait_popup class - image's parent div
from
.apex_wait_popup {
background-color:#FFFFFF;
border:2px solid #666666;
display:block;
font-size:16px;
left:40%;
padding:5px;
<b>position:absolute;</b>
text-align:center;
top:30%;
width:300px;
z-index:1002;
}to
.apex_wait_popup {
background-color:#FFFFFF;
border:2px solid #666666;
display:block;
font-size:16px;
left:40%;
padding:5px;
<b>position:fixed;</b>
text-align:center;
top:30%;
width:300px;
z-index:1002;

Confirm button disabled for Reporter in Solman 7.1 SP10, Incident managment

Hello,
we are using CRM_UI for Incident managment. When the ticket is in status "Proposed Solution" , Reporter is not able to confirm the ticket, "Confirm" button is disabled. How to enable this button?
Renato

Hello Renato,
Please check authoraziton object b_userstat mentioned at belowed thread:
Reporter not able to confirm the Incident in SolMan 7.1 SP6
BR,
K.

BUG - remove hidden information - Acrobat remove some visible/live text (in all Acrobat versions)!!!

hello
I need to check many pdf for hidden/clipped text and remove them. Acrobat can find this BUT have bug.
Acrobat mark some live visible text and this is problem if you click "remove" button.
Here is evidence (6):

It was strange in my copy of DC, but I selected the Redact tool and then remove hidden information. I highlighted the hidden info in both files, but then backed out, not doing the remove. When I tried again, the remove hidden tool was blocked. When I actually did the removal, those items were missing as you mentioned. I am not sure why they were listed as hidden since they were indeed visible. I am not really helping answer the problem, but confirming your results.
Also, if you select remove hidden information when closing the document, you lose these fonts characters just as when using the Redact tool. I would agree that this is indeed an issue for a bug report. An earlier post provided the bug report link and I would suggest using it.

Bug Report E71 - Post (serious) bugs here.

Hi,
Maybe it's wise to have a dedicated bug report topic for the E71.
So not discussions here .. just USEFULL reports.
Bug #1 :
Situation:
- I am having a sip internet-call (native SIP client) with an Asterisk server.
- put the call on 'standby' (by menu Options)
- i press the 'Options' softkey again
- phone freezes. Only battery removal can restart it.
(it also freezes after doing some random key presses .. which i can't remember exactly .. but the standby is not stable.)
Bug #2:
- please fix color-settings for the camera . There is 'purple' all over.

501.21.001 on RM-357 (E71-2) Since upgrading to 501, I've had two major problems. 1) rarely (it's only happened twice), the SMS application will hang when attempting to reply to a message. The original message stays on the screen and nothing will let me out of the app. The phone will respond to the power button, however, and seems to work fine after a reboot. 2) battery life and/or battery meter is terrible. Battery meter will stay near the top then suddenly drop to 2-3 bars remaining. Energy Profiler seems to confirm my power usage is about where it used to be (drawing about 0.12W with the screen off and Gravity running in the background). Phone will then reach 1 bar and give "battery low" warnings, but I'm not convinced the battery is truly low. Last night I was on one bar for over two hours, Gravity was left running, I send and received a few texts, and I was connected to my in-car bluetooth for about 25 minutes, and the phone did not die. On the original firmware, I would never have made it through all that on one bar, which makes me think the bug is with the battery meter, not the battery life itself.

BUG REPORT: iPhone 4 Crashes When Adding Contact to Favorites

Here are the exact steps I went through to reproduce the problem.
Go to settings and set up an exchange account to work with Google Sync. The instructions are here:
http://www.google.com/support/mobile/bin/answer.py?answer=138740&topic=14252
After syncing your contacts, go to the Phone app. Go to Favorites and hit the "+" button to add a favorite. Use the search bar to find a contact (important). Once you find the person you want, select them from the list, and when you do, the app crashes.

I have no idea how to share this bug with Apple.
Go here: http://www.apple.com/feedback/iphone.html and choose *Bug Report* from *Feedback Type* popup menu.
Before doing that though, try to confirm that the same thing happens on other iPhone's and it does it after a reset or restore.

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Bug report: Naming a Bin after creating it with drag'n'drop

There seems to be a small bug when giving a newly created bin a name after creating it by drag'n'drop of several clips onto the "New Bin" icon.
To reproduce:
Select some clips in your project browser
Drag them onto the New Bin button
A new bin is created with the clips in it
- the bin name for it appears to be selected, and editable - just as if you had created a new empty bin by clicking the New Bin button
- type in a new name - it accepts the name fine, now press enter.
- your new name disappears, and *now* you are really in the mode to edit the bin name
- type your name again, and it works.
Work around:
When creating new bins by using drag'n'drop of clips onto the New Bin button, first press enter once to enter into the proper edit mode before giving the bin a new name.
(is there a better place to file bug reports?)
Version 6.0.1 (014 (MC: 264587))
Hardware Overview:
Model Name:          Mac Pro
Model Identifier:          MacPro5,1
Processor Name:          Quad-Core Intel Xeon
Processor Speed:          2.8 GHz
Number Of Processors:          1
Total Number Of Cores:          4
L2 Cache (per core):          256 KB
L3 Cache:          8 MB
Memory:          8 GB
Processor Interconnect Speed:          4.8 GT/s
Boot ROM Version:          MP51.007F.B03
SMC Version (system):          1.39f11
SMC Version (processor tray):          1.39f11
OS X 10.6.8

Er, just answered my question about bug reports by reading the "read this before posting" link above
But I'll leave this here for the work-around in case anyone else needs it.

Bug report submitted re Input Mode affected by ACR 4.2 Mac - very annoying

Just submitted a bug report to Adobe. ACR 4.2, Photoshop 10, Tiger 10.4.10, PowerPC.
Most users in the US and the UK may not even run across this situation.
If you use a non US standard keyboard layout as your Input mode, causing ACR 4.2 to launch, either from Bridge, Photoshop, or the Finder, this switches the selected keyboard to the US standard. If you click the Cancel button in ACR, the keyboard reverts back to your custom keyboard layout; but if you click Open, the US standard keyboard remains set even after quitting Photoshop, ACR and Bridge.
It took me a while to figure out what was causing me to loose my preferred keyboard layout. It didn't dawn on me ACR 4.2 was doing it. Observing a few screen shots led me to discover the cause.
It's most annoying.

The choices in Bridge > Preferences > Advanced > International > Keyboard are limited, and they do not allow for choosing custom keyboard layouts.
I need the custom keyboard layouts for a variety of reasons, such as being able to type in seven languages with my most used one without switching, two Russian layouts to allow for two non-standard ways of encoding Russian fonts, etc.

Bug report: Time stamp misalignment in recent list

Bug report: With the new compact design, go to recent pivot, tap on a conversation, press back button to go back to recent, notice the time stamps to the right of the list have moved even more right, with text being cut off the screen.
Using Lumia 1020 with Cyan and 8.1.1 DP.

I figured this would be the best place to post it so that an Apple representative might see it.
Actually it's not as likely to be seen here since there are so many posts for any Apple rep to have to scan. The best way to report an issue to Apple is through the feedback pages or, if you're a member of Apple's developer program, through the bug reporter.
Regards.

Bug report 02

Bug report 02
In the ScoreWindow
with the INbutton activated
with Quantize 128,384
with Interpretation OFF
with Syncopation OFF
with No Overlap OFF
with the 1/128th NoteSymbol selected in the PartBox :
Playing a note on an external MIDI-keyboard will insert
a 1/64th note instead of the selected 1/128th note.
Anybody experiencing the same problem ?
Kind regards,
Urban Utan
Rotterdam.

or use the Safari button with the bug symbol. There you could easily add a screenshot, sourcecode and problem type of your bug on a html page.
Andreas

Bug Report: New conversation window stills the sys...

Bug Report: Skype Desktop: New conversation window stills the system/keyboard focus.
When the UI is in multi-window mode and a conversation window pops up (due for example to a newly received chat message), that window steals the system/keyboard focus, even though it appears in a minimized state in the Windows taskbar. And this should not happen by default, because it is impractical (especially for screen reader users). And it didn't happen in Skype 6.21 and earlier. But since the new UI was introduced officially in Skype 7.0, it started happening constantly.
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Move the system focus to another application.
7. Tell someone to send you a chat message. When the message arrives and the conversation window pops up minimized in the Windows Taskbar, everything seams to be as it should. A few seconds after that however, the system/keyboard focus gets moved to that new conversation window, even though it is neither restored/maximized (it is minimized), nor it is visible on the screen (except as a button in the taskbar).
Actual results:
When a new conversation window pops up in the Windows taskbar, it stills the system/keyboard focus to itself from the currently focused application.
Expected results:
Skype's popping up new conversation windows should not still the system/keyboard focus to themselfs from the currently focused application.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Sending a bug report on the OS and a sleep mode problem.

I find the bug button in Safari really convenient for sending Apple bug reports. And when other applications crash, you usually get an error dialog with a button to send a bug report. But sometimes problems arise that require reporting, but which don't fall in either of these categories. It would be very handy to have a bug "button" for the OS, or perhaps just a menu selection in the Finder menu bar that invokes a bug report dialog box. I know you can dig around and find the URL for Apple's bug report web page, but I am always forgetting it -- I suppose I could just bookmark it, but then I'd just have to dig around in all the bookmarks to find it. Better would be a utility built-in to the OS for sending bug reports (like Safari's). It could also automatically transfer necessary info about the OS rev and such.
The problem I had was this. I have a script that puts my iMac to sleep. I put the script alias on the task bar and a single click puts the computer to sleep (easier than using the menu). Unfortunately, I sometimes click it by mistake when I am trying to click an adjacent icon in the task bar, and the Mac starts going through its cycle to enter sleep mode and is impervious to anything I do to try and cancel it. I tried pressing the space bar continuously to prevent it from going to sleep, but that did not work. Worse, when it went to sleep and I woke it up again, the task bar would not appear, clicking on app windows did not activate them, Finder menus could not be selected, etc. The cursor would move, but I could not do anything else. (I wish now I had noted if the clock in the menu bar was still advancing, but I didn't think to do that.) I powered down the iMac from the power key and rebooted. Things are working fine now.
I wanted to send a bug report on this, but realized that unlike Safari, there was no button or menu selection for doing that. So here I am.
Any suggestions are welcome.
TIA,
Drake

[email protected]
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Solaris 9 x86 bug report - el_GR.ISO8859-7 & CDE

I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
:0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
in /usr/dt/config/Xservers file, to start the X server.
Here is the $HOME_DIR/.dt/startlog file:
--- ??? 23 ??? 2003 12:10:51
--- /usr/dt/bin/Xsession starting...
--- starting /usr/openwin/bin/speckeysd
--- Xsession started by dtlogin
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing /root/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read /root/.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
--- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/3
Sun Microsystems Inc. SunOS 5.9 Generic_112234-03 November 2002
/usr/dt/bin/ttsession[337]: starting
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
Anyway, I hope this will help developers solve a problem -if it really exists-.
Angelos Vasilopoulos
Site Security Officer
[email protected]

I'm posting this article here, because I can't find any official Solaris 9 x86 bug report page. I hope the developers will notice it. I'm using Solaris 9 x86 (12/02), with the latest 9_x86_Recommended patch cluster installed, and support for Greek installed too.
It seems there is some kind of problem, when trying to view text files with Greek (el_GR.ISO8859-7) characters, which were created under Windows. To be more specific:
If I boot at CDE with language el_GR.ISO8859-7, and try to view a .txt file (just with a simple double click), which I have created under Windows, with Greek characters,
the screen goes black, and the CDE login screen appears again (restarts). If I keep the Greek language or change the language to US English, I can boot at CDE again, with
no problems. If I try "command line logging", the screen goes off - just like when the computer is powered off, and I can't do anything, (well, except pressing the reset button, that's the sure way). And if I use the "init 6" command, while being logged at CDE, from a terminal, the Graphical Desktop exits, and then, the screen goes off again (just like the computer is powered off), but finally the computer manages to restart.
I'm using the Sun X server, NOT the XFree86 porting kit and I use the entry
:0 Local local_uid@console nobody /usr/openwin/bin/Xsun :0 -dpsfileops
in /usr/dt/config/Xservers file, to start the X server.
Here is the $HOME_DIR/.dt/startlog file:
--- ??? 23 ??? 2003 12:10:51
--- /usr/dt/bin/Xsession starting...
--- starting /usr/openwin/bin/speckeysd
--- Xsession started by dtlogin
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing /root/.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read /root/.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /root/.dt/sessionlogs/www_DISPLAY=:0
--- DTSOURCEPROFILE is 'true' (see /root/.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/3
Sun Microsystems Inc. SunOS 5.9 Generic_112234-03 November 2002
/usr/dt/bin/ttsession[337]: starting
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
I don't know if this is a bug or something, and I'm very curious about the cause. I didn't have much time for any other "experiments".
Anyway, I hope this will help developers solve a problem -if it really exists-.
Angelos Vasilopoulos
Site Security Officer
[email protected]

Bug report: Safari 5 fails to handle 8192 bit RSA certificates

Running Safari 5.1.7 on OS X 10.6.8 -- I haven't confirmed for the version of Safari running on 10.7 -- and trying to access a site over https that uses an 8192 bits large RSA cert causes Safari to bug out. It can't display the certificate details correctly, giving just a garbled text output, and even a buggy interface dialog, and manually trying to accept the certificate to get the website to load causes Safari to run in an endless loop, displaying the certificate warning anew, over and over, making it impossible to load the page. The exact same certificate details put in a 4096 bit cert works just fine.
Could anyone in the core dev team take a look at this? The number of sites making use of 8192 bit large certs is growing, and Safari is the only browser out there that can't handle it.
add.: it seems the problem sits at a more fundamental level than in Safari, possibly in some underlying framework - apparently several other applications in OS X fails with handling an RSA cert of 8192 bits size, as mentioned in this thread: https://discussions.apple.com/message/11728527
Possibly related: https://discussions.apple.com/message/3650856

Could anyone in the core dev team take a look at this? The number of sites making use of 8192 bit large certs is growing, and Safari is the only browser out there that can't handle it.
It might be worth registering (for free) as an Apple Developer:
http://developer.apple.com/programs/register/
... and then you can use the Bug Reporter to submit trackable bug reports:
http://developer.apple.com/bugreporter/

Bug report - hidden confirmation buttons in HDR on 13" display

Similar Messages

Maybe you are looking for