Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 24133200C72 for ; Fri, 12 May 2017 21:02:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2284A160BB8; Fri, 12 May 2017 19:02:15 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 68636160BA8 for ; Fri, 12 May 2017 21:02:14 +0200 (CEST) Received: (qmail 91195 invoked by uid 500); 12 May 2017 19:02:08 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 91184 invoked by uid 99); 12 May 2017 19:02:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 May 2017 19:02:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1E266C1AA0 for ; Fri, 12 May 2017 19:02:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Jk_nPtJ62oPX for ; Fri, 12 May 2017 19:02:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id A3E775FDC0 for ; Fri, 12 May 2017 19:02:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D42D7E0D56 for ; Fri, 12 May 2017 19:02:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2CF2524303 for ; Fri, 12 May 2017 19:02:04 +0000 (UTC) Date: Fri, 12 May 2017 19:02:04 +0000 (UTC) From: "Kishore Kumar (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CONNECTORS-1426) New UI doesn't handle connector javascript form checking properly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 12 May 2017 19:02:15 -0000 [ https://issues.apache.org/jira/browse/CONNECTORS-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008560#comment-16008560 ] Kishore Kumar commented on CONNECTORS-1426: ------------------------------------------- Hi [~daddywri], I have fixed the issue. The issue was because I was using the Bootstrap Tab markup, even though we are changing the active tab from the server side. I have removed the {{data-toggle="tab"}} attribute from the HTML so that the Bootstrap javascript event for the tab is not fired. Committed to trunk *r1795008* Thanks, KK > New UI doesn't handle connector javascript form checking properly > ----------------------------------------------------------------- > > Key: CONNECTORS-1426 > URL: https://issues.apache.org/jira/browse/CONNECTORS-1426 > Project: ManifoldCF > Issue Type: Bug > Affects Versions: ManifoldCF 2.7 > Reporter: Karl Wright > Assignee: Kishore Kumar > Fix For: ManifoldCF 2.8 > > > When a connector has javascript that checks for Configuration form legality via the checkConfig() method, switching tabs causes the UI to get confused. Sequence to reproduce: > (1) Create or edit a connector configuration with a checkConfig() method > (2) Click on a tab that has some checking > (3) Modify a field so that it is illegal > (4) Click on another tab > - The proper error message is indeed displayed > - The user clicks "OK" to cancel the alert > - The proper tab continues to be displayed > - The *selected* tab changes, and it *should not* > If you then click "Save", you will be incorrectly told that there is another connection of the same name. > You can try this easily by creating a SharePoint connection, going to the Server tab, and supplying a non-integer for the port number. Then click on the Throttling tab and see what happens. -- This message was sent by Atlassian JIRA (v6.3.15#6346)