Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Oct 2011
    Posts
    54
    Vote Rating
    0
    DarekKay is on a distinguished road

      0  

    Default NumberField bug

    NumberField bug


    It seems, like all number based field widgets are broken (see SpinnerField as well).

    The value within the NumberField doesn't seem to be saved properly:
    Code:
    public void onModuleLoad()
    {
        final NumberField<Integer> number = new NumberField<Integer>(new IntegerPropertyEditor());
        final TextField text = new TextField();
        TextButton button = new TextButton("muh");
    
        button.addSelectHandler(new SelectHandler()
        {
            @Override
            public void onSelect(SelectEvent event)
            {
                number.validate();
                text.validate();
            }
        });
    
        text.addValidator(new EmptyValidator<String>());
        number.addValidator(new EmptyValidator<Integer>());
    
        VerticalLayoutContainer con = new VerticalLayoutContainer();
        con.setBorders(true);
        con.add(text, new VerticalLayoutData(1, -1));
        con.add(number, new VerticalLayoutData(1, -1));
        con.add(button, new VerticalLayoutData(1, -1));
        con.setPixelSize(400, 500);
        RootLayoutPanel.get().add(con);
    }
    And here are the steps:
    1. focus textfield
    2. focus numberfield => textfield blurs => textfield got an error marker
    3. focus textfield again => numberfield blurs => numberfield got an error marker
    Everything fine so far
    1. type something into the textfield, focus numberfield => marker gone
    2. type a number into the numberfield, focus the textfield again => marker still there
    Even a validation using the button doesn't seem to change anything. It seems, like the field updates its value on blur event only once.

  2. #2
    Sencha User
    Join Date
    Jul 2011
    Posts
    25
    Vote Rating
    1
    IgyBoy is on a distinguished road

      0  

    Default


    I can also confirm this kind of behavior.
    First I thought that it has something to do with my code,but going through source i saw that value is not saved properly.

    Using 3.0beta2.

  3. #3
    Sencha User
    Join Date
    Nov 2011
    Posts
    23
    Vote Rating
    0
    pete_by is on a distinguished road

      0  

    Default


    Looks like this issue is related with the one I reported earlier:

    http://www.sencha.com/forum/showthre...e-field-value-
    correctly-under-some-conditions-(BETA2)

  4. #4
    Ext GWT Premium Member
    Join Date
    Oct 2008
    Posts
    126
    Vote Rating
    1
    jonjanisch is on a distinguished road

      0  

    Default Confirmed still exists beta4

    Confirmed still exists beta4


    Confirmed this problem still exists in beta4. I'm not sure if it's the exact same bug. Is this being looked at? I don't see any replies in either thread. Seems like a fairly critical bug. It might be browser related. I'm using Firefox 10.0.2

    My example is very simple.

    1. Upon module start, click "Save"

    Value: null

    2. Input "1" and click "Save"

    Value: null

    3. Input "2" and click "Save"

    Value: 2

    Code:
    public class Example extends Composite {
    
    
        private NumberField<Integer> numberField = new NumberField<Integer>(new IntegerPropertyEditor());
        
        private Button gwtButton = new Button("Save");
        
        public Example() {
            VerticalPanel vp = new VerticalPanel();
            vp.setPixelSize(400, 300);
            vp.add(numberField);
            vp.add(gwtButton);
            gwtButton.addClickHandler(new ClickHandler() {
                @Override
                public void onClick(ClickEvent event) {
                    GWT.log("Value: " + numberField.getValue());
                }
            });
            initWidget(vp);
        }
    }
    Last edited by jonjanisch; 19 Mar 2012 at 1:50 PM. Reason: Added browser info

  5. #5
    Sencha User WesleyMoy's Avatar
    Join Date
    Oct 2009
    Location
    Redwood City, California
    Posts
    402
    Vote Rating
    2
    WesleyMoy is on a distinguished road

      0  

    Default


    We've made some changes to NumberField recently for mostly unrelated bugs. I've tried both DarekKay's and jonjanisch's test cases, and I can't seem to reproduce the issue with the latest code from subversion.

    If you're building from subversion, please test with the latest source. If not, try this out again when the next release rolls around and see if you still notice the issue.

  6. #6
    Ext GWT Premium Member
    Join Date
    Oct 2008
    Posts
    126
    Vote Rating
    1
    jonjanisch is on a distinguished road

      0  

    Default


    Thanks Wesley.

    For completeness, I tested both my example and Darek's code in both Firefox 10.0.2 and Chrome 17 and was able to reproduce both problems in beta4.

    I don't think it matters, but in my example I'm using a GWT button. I ran Darek's with a ExtGWT TextButton.

    I'm using GWT 2.4.0 with GXT beta4.