#4095 NORM Untriag: Switching to "real" Abiword mode, opening 'Open' dialog box, and switching to browser leaves Write in bad state.

Zarro Boogs per Child bugtracker at laptop.org
Mon Oct 8 03:17:34 EDT 2007


#4095: Switching to "real" Abiword mode, opening 'Open' dialog box, and switching
to browser leaves Write in bad state.
--------------------------------------+-------------------------------------
 Reporter:  sleet01                   |       Owner:  uwog     
     Type:  defect                    |      Status:  new      
 Priority:  normal                    |   Milestone:  Untriaged
Component:  write-activity (abiword)  |     Version:           
 Keywords:                            |    Verified:  0        
--------------------------------------+-------------------------------------
 '''Overview'''

 I was hoping to use the Abiword 'real' mode, unlocked by hitting
 <ctrl>+<n> in the Write activity, to edit config files without going into
 the developer console (which has a couple problems as a general-use
 editor).  When I found that I couldn't paste the file name in to the
 filename address bar in the 'Open' dialog, I switched back to the Browser
 to try to memorize the name.  When I switched back to Write, however, I
 found it was once again in standard mode and would not accept any input.
 The cursor properly changed to a pointer or text select cursor depending
 on its position over the screen, but I couldn't see the dialog box or use
 any of the tabs or icons that were displayed.  I also couldn't stop the
 Write activity from the Home activity donut icon's context menu.


 '''Steps to Reproduce'''

 1) Start Browser
 2) Go Home; start Write from the bottom Activity launcher
 3) Press <ctrl>+<n> to switch to Abiword mode.
 4) Press the 'Open' icon to launch the open dialog
 5) Click on the small 'Enter File Name' icon at the top-left of the dialog
 6) Switch back to home and go to the browser
 7) Switch back to the Write activity


 '''Actual Results'''

 Upon returning to the Write activity Write was unresponsive, although no
 other UI elements or activities suffered from any slowdown.  I believe the
 Abiword interface was still running, but hidden by the standard interface.
 I couldn't stop the Write activity, and wanted to reboot anyway to get
 debug logging activated, so I didn't spend any more time investigating
 whether the Abiword interface was actually receiving events.


 '''Expected Results'''

 If a program or activity offers a second, 'secret' interface, one of two
 things should occur upon leaving and returning to the activity:
 1) The original interface should be restored *and* work correctly.
 2) The 'secret' interface should remain in place upon return.


 '''Build Date And Platform'''

 Build 613 pre-built VM on VirtualBox


 '''Additional Information'''

 I'm not sure if this is a Write-specific failing or more related to
 Tinderbox or Sugar, but I'll file it as a Write activity component bug
 since that's the only place I've seen it to date.

-- 
Ticket URL: <https://dev.laptop.org/ticket/4095>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system



More information about the Bugs mailing list