Intersoft Community - Chrome

Chrome with new version has introduced a new problem

sjain — Thu, 08 Nov 2018 14:11:39 GMT

Hi,

Chrome with new version has introduced a new problem.

On click on any cell of webgrid, cell text ended with space which tuns into "\t" into database while save. which is causing issues.

(Unable to Attached images).

NOTE: Chrome earlier version (67.0) is working fine.

I am using Webgrid product version 10.0.

Please give us a solutions.

Regards

Sachin Jain

Calendar control failure in chrome browser inside grid

sjain — Tue, 05 Dec 2017 12:41:04 GMT

Hi,

Calendar control inside grid is not working into chrome browser.

There is some javscript error is coming which has been attached.

There is already thread is running for this but No REPLY from your side.

https://www.intersoftsolutions.com/Community/WebGrid/Loading-the-Calendar-control-failure-in-chrome-browser/

Please give us solutions.

Regards

Sachin Jain

WebGrid not showing in Google Chrome with a .Net Framework 4 project

Padma — Fri, 25 Mar 2016 09:43:00 GMT

The Grid is not loading in Google Chrome .But works in different other browsers like IE and FireFox. Kindly let me know if the error is already been reported and also kindly give me a work around. PFB the error in chrome browser :

I use the below version.

.Net framework - 4.5

ISNET.dll - 3.0.5000.558

ISNET.WEBUI.WEBGRID.dll - 6.0.7200.104

ISNET.WEBUI.dll - 3.0.5000.558

ISNET.WEBUI.WEBSCHEDULER.dll - 1.0.1000.104

ISRes.axd?F/ISCore.js/305000558:7Uncaught TypeError: window.attachEvent is not a function(anonymous function) @ ISRes.axd?F/ISCore.js/305000558:7

ISRes.axd?S/WebScheduler.js/101000104:7Uncaught TypeError: window.attachEvent is not a function(anonymous function) @ ISRes.axd?S/WebScheduler.js/101000104:7

ISRes.axd?S/WebScheduler_Calendar.js/101000104:7Uncaught TypeError: window.attachEvent is not a function(anonymous function) @ ISRes.axd?S/WebScheduler_Calendar.js/101000104:7

ISRes.axd?F/ISCore.js/305000558:7Uncaught TypeError: document.body.attachEvent is not a functionRegisterKeyboardHandler @ ISRes.axd?F/ISCore.js/305000558:7(anonymous function) @ ISRes.axd?D/WebMenu.js/252007:7

ISRes.axd?F/ISCore.js/305000558:7 Uncaught TypeError: window.attachEvent is not a function(anonymous function) @ ISRes.axd?F/ISCore.js/305000558:7

ISRes.axd?S/WebScheduler.js/101000104:7 Uncaught TypeError: window.attachEvent is not a function(anonymous function) @ ISRes.axd?S/WebScheduler.js/101000104:7

ISRes.axd?S/WebScheduler_Calendar.js/101000104:7 Uncaught TypeError: window.attachEvent is not a function(anonymous function) @ ISRes.axd?S/WebScheduler_Calendar.js/101000104:7

ISRes.axd?F/ISCore.js/305000558:7 Uncaught TypeError: document.body.attachEvent is not a functionRegisterKeyboardHandler @ ISRes.axd?F/ISCore.js/305000558:7(anonymous function) @ ISRes.axd?D/WebMenu.js/252007:7

Thanks.

WebMenuBar PlaceHolder Width in Chrome

hsevand@tepum.com.tr — Fri, 23 Oct 2015 13:51:10 GMT

Hi,

If you resize Chrome Window by decreasing the width enough, Chrome adds a style attribute width="0%" to td element of placeholder. As a result, after you increase the width of Chrome window, the other td elements of menubar expands and window buttons seem weird.

How can we fix this problem? I attached before and after images of menu bar.

After resizing html:

<table border="0" cellspacing="2" cellpadding="0" width="100%" height="100%" style="table-layout:fixed">	<tbody>
		<tr>
			<td class="dskTskBarButNrml" title="" style="width: 150px;">
				<div style="overflow:hidden; text-overflow: ellipsis; width:100%"><nobr> <img src="/Rhapsody.Web.UI.Presenter/ISRes.axd?D/is_window-16.gif" align="absmiddle"> Talep Yönetimi</nobr></div>
				<div id="divCloseTab" style="top: 3px; left: 259px; position: absolute; display: none;"><img style="text-align:right;vertical-align:top;width:13px;height:13px;cursor:pointer" title="Kapat" src="/Images/WebDesktop/CloseSmall.gif" onclick="closeWindowWithSaveControl2('Lst1400');"></div>
			</td>
			<td class="dskTskBarButNrml" title="" style="width: 150px;">
				<div style="overflow:hidden; text-overflow: ellipsis; width:100%"><nobr> <img src="/Rhapsody.Web.UI.Presenter/ISRes.axd?D/is_window-16.gif" align="absmiddle"> Varlık Yönetimi</nobr></div>
				<div id="divCloseTab" style="top: 3px; left: 1189px; position: absolute; display: none;"><img style="text-align:right;vertical-align:top;width:13px;height:13px;cursor:pointer" title="Kapat" src="/Images/WebDesktop/CloseSmall.gif" onclick="closeWindowWithSaveControl2('Lst508');"></div>
			</td>
			<td placeholder="true" width="100%" style="width: 0%;"> </td>
		</tr>
	</tbody>
</table>

How can I fix this problem?

WebGrid 7 and Chrome 43 Hotfix

vangorpj — Thu, 25 Jun 2015 20:10:03 GMT

Hi,

I am currently supporting an older application that is using WebGrid version 7.0.7200.401 (along with ISDataSource). The grid no longer works under Chrome 43. I understand that there is currently a hotfix available to resolve this but can anyone clarify if this patch would also work for WebGrid 7 or is the patch specifically targeted for version 8 and 9?

WebGrid causing JavaScript errors in Telerik control

aliard@sigma-rh.com — Thu, 18 Jun 2015 15:20:34 GMT

Hi,

We are in the process of replacing our old menu component by Telerik's RadMenu. During our testing we discovered that as soon as there is a WebGrid (also occurs with a WebTextEdotir) present on the page, we receive a lot of JavaScript errors from Telerik's event handlers. On pages where there is no WebGrid, we don't have those errors.

The errors are present in IE11, Firefox and Chrome, but not un IE versions prior to 11 (no errors in IE10, 9, etc). See the attached screenshots for an example of the errors we get. In this example, the ScriptResource.axd is "MicrosoftAjax.js". and the "e" parameter received correspond to the event argument expected by the event handler "g" in NavigationScripts.js, which "g" doesn't receive as the calling function in IE11.js (or IEMozBridge.js) doesn't specify any argument when calling it.

My undestanding from these errors and their stack traces is that the errors are caused by your legacy IE behavior emulation engines found in IE11.js and IEMozBridge.js.

How can we can a solution for this very serious issue, of your scripts files breaking other components ?

Regards,
Alexandre