Announcement

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

    Rich Text Editor problems with Google Chrome and 8.3

    Hi,

    We are having problems with the Rich Text Editor and Google Chrome in 8.3. No such problems with Firefox or IE. But, with Chrome, we can't enter text into a blank Rich Text Editor. If we default some text into the Editor, then we can edit that text and alter the contents of the Editor without a problem. We've been trying to recreate in your Feature Explorer but we can't and we've been playing "options bingo" with our Rich Text Editor but can't figure out what is happening. Do you have any suggestions how we can debug this further?

    #2
    If you're not on a recent build, you'll need to update - this was an issue a while back (a month or so), but has been addressed for a while.

    Comment


      #3
      We are using the nightly from 3/25 I just upgraded this week hoping it would be resolved. So, how can I debug further?

      Comment


        #4
        What doctype/OS are you using? Can you show the basic code that fails for you (ie, the RichText class you're creating and the list of settings you're using)

        Comment


          #5
          Our doctype looks like this right above the <html> tag. Is this accurate?
          <!DOCTYPE html>

          We are testing with Windows 7 currently. Haven't tried any other OS yet.

          Field definition:
          Code:
          {name:"notes", type:"richText", showTitle:false,  width:"*", colSpan:4,height:395, prompt:"Enter Notes here"}
          Form definition:
          Code:
          	isc.ATDynamicForm.create({
          		ID:"assetNotesEditor",
          	  	overflow: "auto",
          	  	itemHoverAlign:"left",
          		itemHoverHeight:100,
          		itemHoverWidth:200,
          		height:530,
          		numCols:4,
          		width:850,
          		colWidths:[100,80,80,"*"],
          		dataSource:AssetNotes,
          	    emptyMessage:"Select an Asset"
          	});

          Global Form Properties:
          Code:
          	isc.defineClass("ATDynamicForm", "DynamicForm").addProperties({
          		disableValidation:!CLIENT_VALIDATORS_ENABLED,
          		autoDraw: false,
          		autoFocus:true,
          		showErrorText:false,
          		itemHoverDelay:FORM_HOVER_DELAY,
          		itemHoverWidth:400,
          	    errorOrientation:"left",
          	    requiredTitlePrefix:REQUIRED_TITLE_PREFIX,
          		requiredTitleSuffix:REQUIRED_TITLE_SUFFIX,
          		unknownErrorMessage:PROMPT_UNKNOWN_ERROR,
          		showErrors:function(){
          			showErrorsFormatter(this.getErrors(),this,false);
          		},
          		validate:function(validateHiddenFields){
          			
          			//3/14/13..trim and strip empty strings
          	    	var editValues = this.getValues();
          	    	var newEditValues={};
          	        var editKeys = isc.getKeys(editValues);
          	        var j = editKeys.length;
          	        for (var i = 0; i < j; i++){
          	        	var editKey = editKeys[i];
          	          	var editValue = editValues[editKey];
          
          	          	if(this.dataSource!=null && this.dataSource.ID=="CustomField" && editKey=="defaultValue"){
          	          		if(isA.Date(editValue)){
          	          			editValue = editValue.toString();
          	          		}
          	          	}
          	          	if(this.dataSource!=null && this.dataSource.ID=="CustomFieldInstance" && editKey=="value"){
          	          		if(isA.Date(editValue)){
          	          			editValue = editValue.toString();
          	          		}
          	          	}
          	          	
          	          	if(isA.String(editValue)){
          	          		editValue = editValue.trim();
          	          		if(editValue==""){
          	          			editValue=null;
          	          		}
          	          	}
          	          	newEditValues[editKey]=editValue;
          	        }
          	        this.setValues(newEditValues);
          			
          	        var success = this.Super("validate", arguments);
          	        return success;
          			
          		},
          		handleHiddenValidationErrors:function(hiddenErrors){
          			var allErrors = this.getErrors();
          			var allErrorsKeys = isc.getKeys(allErrors);
          			var hiddenErrorsKeys = isc.getKeys(hiddenErrors);
          			//only display hidden errors if there are no visible errors
          			//as evidenced by seeing if getErrors returns a larger list than 
          			//the errors passed to this function
          			if(allErrorsKeys.length<=hiddenErrorsKeys.length){
          				showErrorsFormatter(hiddenErrors,this,true);
          			}
          		}
          	})

          Comment


            #6
            Hi, is there anything I can do to help with this issue? Is there some extra debugging I can turn on that will show what is happening in our environment?

            Comment


              #7
              Sorry, we can't run the code above, it doesn't suggest any particular cause (looks like ordinary usage), so this is something where you'll need to try to isolate something we can look at to reproduce the issue.

              Comment


                #8
                Understood, that's why I was asking if you could provide some debugging tips. For instance, are there any console logging categories I can set to debug? Anything else I can do? I'm at a loss on how to debug this further on our side now. And, I don't know how to recreate on your side.

                Comment


                  #9
                  We can't really do over-the-shoulder debugging without taking up far more of your time than it would take to just isolate the issue.

                  It's not really ever possible to be at a loss for how to isolate something.. just remove differences until you find the factor that makes the issue appear.

                  Comment


                    #10
                    Ok, I was just hoping there would be some shortcut to help with debugging. It is just very time consuming to try to isolate problems like this. So, I really meant I'm at a loss for how to do this without a huge time drain. So, we've got a workaround in place on our side and we'll just leave it at that for now.

                    Comment


                      #11
                      We've made a change to 8.3p and 9.0d that should get this working for you - please retest with a nightly build dated April 20 or later

                      Comment


                        #12
                        word bullets are missing

                        Hi all

                        Using with mouse options copy and past the below bullets data from word to rich text editor in Chrome Browser, the data bullts are missing and also one line date is showing in two are more line( screen-2 ie.. ), please help me.
                        Even i changed the chrome properties of Target "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" -user-agent="Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)"


                        Screen-1

                        Skills:
                        The North Carolina Department of Justice (NC-DOJ) is seeking to fill a short term (approx. 12 month) contractor to assist with the re-engineering of the current Sex Offender Registry (SOR) solution as the NC-DOJ migrates towards compliance with the federal Sex Offender Registry Notification Act (SORNA).

                        Knowledge and Skills Required:
                        • Strong Business Analyst Skills
                        • MS Access
                        • C#
                        • ASP.net
                        • Web Services
                        • Entity Framework
                        • Team Foundation 2010
                        • SQL Server 2008 R2


                        Screen -2

                        Skills:

                        The
                        North Carolina Department of Justice (NC-DOJ) is seeking to fill a short term
                        (approx. 12 month) contractor to assist with the re-engineering of the current
                        Sex Offender Registry (SOR) solution as the NC-DOJ migrates towards compliance
                        with the federal Sex Offender Registry Notification Act (SORNA).

                        Knowledge
                        and Skills Required:

                        Strong
                        Business Analyst Skills

                        MS
                        Access


                        C#

                        ASP.net


                        Web
                        Services

                        Entity
                        Framework


                        Team
                        Foundation 2010

                        Comment

                        Working...
                        X