Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    SelectList issue

    SC Build 06-17-11. If a completely standalone testcase is needed please let me know.

    Scroll all the way to the right and click on the dropdown. You'll notice the main screen has expanded to the grey area. Close the dropdown and try to go all the way back to the left where the tree is. You'll notice that part of it is completely cut off. In Firefox, the layout does not expand at all, but cuts off the dropdown list

    Code:
    isc.HLayout.create({
    ID :"HL",
    members: [
    (isc.DynamicForm.create({
        width: 1800,
        showEdges: true,
        numCols: 4,
        fields: [
            {title:"text", type: "text"},
            {
             type: "select",
             valueMap: {"8":"bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb","7":"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"},
             align: "right"
            }
          
        ]
    }))]})
    Last edited by acarur01; 15 Aug 2011, 04:27.

    #2
    This looks like it may be an issue in the feature explorer only.
    What you're describing sounds like an issue whereby, because page-level scrollbars are suppressed in the Feature Explorer, if something exceeds the scrollable space it's either clipped by the browser window (as in FF), or if focus goes to it, the browser will natively scroll it into view, but without showing scrollbars allowing you to scroll back to origin.

    Is this actually effecting you in a real-world usage? If so can you give us a little more info on how exactly its manifesting in your use-case / what the expected behavior is (and perhaps show a simple standalone example we can run outside the Feature Explorer that shows the problem)

    Thanks
    Isomorphic Software

    Comment


      #3
      Yes, this is happening in an application but when we extract it as a standalone, (and without feature explorer) we cannot reproduce it. The most I can provide at the moment is a screenshot.

      Comment


        #4
        From the screenshot this does look like it may be being caused by suppressing page level scrollbars within your application as we described above.

        If you allow page level scrollbars to show is the behavior more intuitive? Would this be an acceptable solution for your application?

        Comment

        Working...
        X