franky1978 / igoogle-legacy

Automatically exported from code.google.com/p/igoogle-legacy
1 stars 0 forks source link

Getting Started: Legacy Gadgets API - editor - xmlversion space expected #572

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Description of the bug/feature.
==================================
With google chrome, xml tag bad formed in the GGE at 
http://code.google.com/intl/fr/apis/gadgets/docs/legacy/gs.html#GGE

PLEASE FILL OUT THE FOLLOWING FOR A BUG REPORT ONLY:

What steps will reproduce the problem?
======================================
1. Go to http://code.google.com/intl/fr/apis/gadgets/docs/legacy/gs.html#GGE
2. scroll down to the GGE
3. Select the preview sheet

What is the expected output?
============================
Expected output is a gadget

What is the actual output?
==========================
Erreur d'analyse du module spec :
ligne 1, colonne 38
  <?xmlversion="1.0" encoding="UTF-8"?> 
Erreur d'analyse XML :
ParsePI: PI xmlversion space expected 

Which browsers have you experienced this on?
============================================
Only with google chrome.
Works fine with IE and firefox.

Which operating systems have you experienced this on?
=====================================================
Windows VISTA

Please provide any additional information below.

------------- DIAGNOSTIC --------------------------
XML :
<?xmlversion="1.0" encoding="UTF-8"?>
Should be instead :
<?xml version="1.0" encoding="UTF-8"?>
(with a space between xml and version, works fine by adding manualy)

In IE and Firefox, the text editor start in insert mode
In Chrome, the text editor start in replace mode with the cursor at the 
missing caracter. It seems like the editor erase the space at the opening.

Original issue reported on code.google.com by jdesesqu...@gmail.com on 4 Jul 2009 at 7:43

GoogleCodeExporter commented 9 years ago
Unfortunately, there are known issues in the text engine driving GGE while using
WebKit browsers. I suspect this is an instance of one of those issues, and is
unlikely to be fixed.

Original comment by api.dwh%...@gtempaccount.com on 13 Jul 2009 at 7:16

GoogleCodeExporter commented 9 years ago
You're not going to fix your own text editor in your own browser?

Original comment by hcarter333@gmail.com on 24 Sep 2010 at 12:15