Re: Jira problem

Hi Tucker,

I just tried to reproduce this bug but cannot repeat that behavior.
So, I cloned that bug (LPP-8240) and re-attached the file and it seems 
fine.
I deleted LPP-8238.

If this continues to happen or if anyone else sees it, please let us 
know.

--- Amy

On Sun, May 31, 2009 at 6:07 PM , P T Withington wrote:

> I created a new bug:
>
> [[#LPP-8238] Debugger component window scrolls poorly in DHTML - 
> OpenLaszlo Jira](http://jira.openlaszlo.org/jira/browse/LPP-8238)
>
> and somehow it is marked as 'fixed', but it really is brand new.  I 
> can't seem to make it un-fixed.  Any ideas?  Is anyone else seeing 
> this problem?

Re: Jira problem

Tucker - I just reproduced the problem and fixed it (I hope).
When a new bug was filed, the status was correct. As soon
as you edit it to add the "Fix Version" and the "Priority",
a "Resolution" field preset to "Fixed" was on that form.
That's why it was new, but set to Fixed. I removed that
field because it shouldn't have been on the form. This
seems to have fixed the problem.

Let me know if it continues to happen.
--- Amy

On Mon, Jun 1, 2009 at 9:13 AM , Amy Muntz wrote:

> Hi Tucker,
>
> I just tried to reproduce this bug but cannot repeat that behavior.
> So, I cloned that bug (LPP-8240) and re-attached the file and it seems 
> fine.
> I deleted LPP-8238.
>
> If this continues to happen or if anyone else sees it, please let us 
> know.
>
> --- Amy
>
>
> On Sun, May 31, 2009 at 6:07 PM , P T Withington wrote:
>
>> I created a new bug:
>>

Re: Jira problem

Thanks!

It's odd that there is no way to directly reset that field.

On Jun 1, 2009, at 9:23, Amy Muntz <amuntz <at> laszlosystems.com> wrote:

> Tucker - I just reproduced the problem and fixed it (I hope).
> When a new bug was filed, the status was correct. As soon
> as you edit it to add the "Fix Version" and the "Priority",
> a "Resolution" field preset to "Fixed" was on that form.
> That's why it was new, but set to Fixed. I removed that
> field because it shouldn't have been on the form. This
> seems to have fixed the problem.
>
> Let me know if it continues to happen.
> --- Amy
>
>
> On Mon, Jun 1, 2009 at 9:13 AM , Amy Muntz wrote:
>
>> Hi Tucker,
>>
>> I just tried to reproduce this bug but cannot repeat that behavior.
>> So, I cloned that bug (LPP-8240) and re-attached the file and it  
>> seems fine.
>> I deleted LPP-8238.
>>
>> If this continues to happen or if anyone else sees it, please let  
>> us know.
>>

Unprintable characters being displayed in IE7/IE8

Hi Max,

I created LPP-8244 to track an issue where CTRL-SHIFT-P displays a 
box-like character in  input text. This happens only in IE running in 
SWF/SWF9. This is the last remaining issue from LPP-7896 and I don't 
know if there is anything we can do about it. This key works fine as a 
command sequence but it displays the box character in the input box.

Any thoughts?

Thanks!

Phil

Losing mouse clicks in SWF8 (LPP-7981) when setFocus() is used

Hi Max,

Perhaps you (or somebody on laszlo-dev) has some thoughts on 
http://www.openlaszlo.org/jira/browse/LPP-7981. This is a swf8-only 
issue (at least on a PC). If you open a window with a button that is 
displayed under the mouse, the button requires 2 clicks if the focus has 
been set to another element on the window. If the user moves the mouse a 
single pixel, the button receives the very next click. At first I looked 
for a general solution but right now I'm looking for a workaround in the 
application. The other way to make it work is to NOT call setFocus() and 
the button is clickable.

Andre added a simpler testcase that mostly uses native Flash code.

I have not found a workaround. I tried to simulate a mouseover event on 
the button but I don't think Flash likes me hijacking mouse events.

Any thoughts?

Thanks!

Phil

Re: Max size to lz.DataElement

(ccing laszlo-dev)

Not that I know of.  André recently fixed a bug in Firefox DHTML that 
could be related - see http://jira.openlaszlo.org/jira/browse/LPP-8214 
for more details.

Can you give me more information about where this could be occurring?

Matt Kolenda wrote:
> Amy/Max
> 
> Is there a maximum amount of data that can be put into a lz.DataElement 
> object?
> 
> Matt

--

-- 
Regards,
Max Carlson
OpenLaszlo.org

For Review: Change 20090601-maxcarlson-6 Summary: Fix contextmenu inconsistencies in DHTML

Change 20090601-maxcarlson-6 by maxcarlson <at> Bank on 2009-06-01 17:44:36  
PDT
     in /Users/maxcarlson/openlaszlo/trunk-clean
     for http://svn.openlaszlo.org/openlaszlo/trunk

Summary: Fix contextmenu inconsistencies in DHTML

Bugs Fixed: LPP-8218 - DHTML: issues with contextmenu onmenuopen,  
dragging

Technical Reviewer: andre.bargull <at> udo.edu
QA Reviewer: hminsky

Details: This includes all changes from
http://www.openlaszlo.org/pipermail/laszlo-dev/2009-May/021166.html 
  - Andre's changes to improve context menu support.  I had to hand- 
merge LzKeyboardKernel due to changes I'd made related to LPP-8210.

LzSprite -  [Andre: canceling event-bubbling for all mouse-events =>  
this was already done for all browsers (except Firefox) and all events  
(except onmouseup). Why wasn't Firefox affected? => All other browsers  
set "event.keyCode" to '0' for mouse-events, only Firefox sets  
"keyCode" to 'undefined'. Now take a look at  
"LzKeyboardKernel.__keyboardEvent()", every event was canceled in that  
function if "keyCode" was '>= 0'!]

Moved detectstuckkeys from capabilities to quirks.  Added  
quirks.noglobaloncontextmenu  to deal with Firefox OS X context menu  
issue - https://bugzilla.mozilla.org/show_bug.cgi?id=443191.   
__clickDispatcher() looks for quirks.noglobaloncontextmenu to fix  

Re: Max size to lz.DataElement

I don't think so - there was one in DHTML for some browsers (LPP-8214) 
but hypothetically there shouldn't be.  I'd suggest testing for this though!

Matt Kolenda wrote:
> Max
> 
> This is more of a hypothetical question.   In Flash 8 we were limited to 
> display only the first 100K of a message on the client.  With DHTML we 
> will no longer be limited by flash 8.  However the platform may have 
> imposed a similar restriction.  Is there a size restriction?
> 
> Matt
> 
> 
> On Mon, Jun 1, 2009 at 5:38 PM , Max Carlson wrote:
> 
>> (ccing laszlo-dev)
>>
>> Not that I know of.  André recently fixed a bug in Firefox DHTML that 
>> could be related - see http://jira.openlaszlo.org/jira/browse/LPP-8214 
>> for more details.
>>
>> Can you give me more information about where this could be occurring?
>>
>> Matt Kolenda wrote:
>>> Amy/Max
>>>
>>> Is there a maximum amount of data that can be put into a 
>>> lz.DataElement object?
>>>

Re: For Review: Change 20090601-maxcarlson-6 Summary: Fix contextmenu inconsistencies in DHTML

still don't know why the text selection gets cleared when you move the mouse out of a textfield in Firefox