Hi there! I have the following problem and don''t know how to come by this. If I include prototype.js and scriptaculous.js Safari gets a problem with coloring the background of the viewport. It only works where you placed some div, the rest of the page won''t be correctly colored at first. If you resize the window everything is fine. I did test this with Safari 2.x/3.x on OS X 10.4.11, other browsers (FF 1.5+, Camino, Opera 9, IE 6+ on Win) are fine with this page. Also confirmed by other Mac Users using various OS X versions and Safari versions. Here you can take a look at the issue <http:// www.fightex.com/test> and here you can find a screenshot <http:// www.fightex.com/test/scr_safari_scriptaculous_bg_issue.png> Scriptaculous Version: 1.8.0 Prototype Version. 1.6.0 Thanks, steffn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hi Steffn I''m glad you posted this. I noticed the same thing on one of my sites when I upgraded to Scriptaculous 1.8/Prototype 1.6. I also discovered that switching tabs is enough to have the background drawn properly. I validated my HTML and CSS and decided it was a bug in Safari, so I submitted it to Apple. It is odd that it happened with the upgrade of Scriptaculous/Prototype, but since all other browsers I''ve tried work fine, I guessed it was an oddity in Safari that just became apparent with the latest js libraries. If you (or someone else) determines otherwise, I''d be happy to hear about it. Peace, Phillip On Nov 26, 3:42 am, ftx <ste...-RbZlAiThDcE@public.gmane.org> wrote:> Hi there! > > I have the following problem and don''t know how to come by this. If I > include prototype.js and scriptaculous.js Safari gets a problem with > coloring the background of the viewport. It only works where you > placed some div, the rest of the page won''t be correctly colored at > first. If you resize the window everything is fine. > > I did test this with Safari 2.x/3.x on OS X 10.4.11, other browsers > (FF 1.5+, Camino, Opera 9, IE 6+ on Win) are fine with this page. Also > confirmed by other Mac Users using various OS X versions and Safari > versions. Here you can take a look at the issue <http://www.fightex.com/test> and here you can find a screenshot <http://www.fightex.com/test/scr_safari_scriptaculous_bg_issue.png> > > Scriptaculous Version: 1.8.0 > Prototype Version. 1.6.0 > > Thanks, > steffn--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
HI! "Good" to hear I am not the only one recognizing this behavior. I can only tell you that it is totally reproduceable in Safari 3.0.4 (523.12) as well as on 2.0.4 (419.3). If I only link the prototype.js everything is fine again <http://www.fightex.com/test/ index_noscript.html>. As soon as scriptaculous.js is referenced the page background gets broken again. As far is i figured out there were no errors on the javascript console, and I have no idea how to get more close to the reason why this is happening. If any one more familiar with the sources of scriptaculous could take a look at this, it would be really great! Cheers, Steffn On Nov 26, 5:51 pm, Phillip Koebbe <phillipkoe...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hi Steffn > > I''m glad you posted this. I noticed the same thing on one of my sites > when I upgraded to Scriptaculous 1.8/Prototype 1.6. I also discovered > that switching tabs is enough to have the background drawn properly. > I validated my HTML and CSS and decided it was a bug in Safari, so I > submitted it to Apple. It is odd that it happened with the upgrade of > Scriptaculous/Prototype, but since all other browsers I''ve tried work > fine, I guessed it was an oddity in Safari that just became apparent > with the latest js libraries. If you (or someone else) determines > otherwise, I''d be happy to hear about it. > > Peace, > Phillip > > On Nov 26, 3:42 am, ftx <ste...-RbZlAiThDcE@public.gmane.org> wrote:> Hi there! > > > I have the following problem and don''t know how to come by this. If I > > include prototype.js and scriptaculous.js Safari gets a problem with > > coloring the background of the viewport. It only works where you > > placed some div, the rest of the page won''t be correctly colored at > > first. If you resize the window everything is fine. > > > I did test this with Safari 2.x/3.x on OS X 10.4.11, other browsers > > (FF 1.5+, Camino, Opera 9, IE 6+ on Win) are fine with this page. Also > > confirmed by other Mac Users using various OS X versions and Safari > > versions. Here you can take a look at the issue <http://www.fightex.com/test> and here you can find a screenshot <http://www.fightex.com/test/scr_safari_scriptaculous_bg_issue.png> > > > Scriptaculous Version: 1.8.0 > > Prototype Version. 1.6.0 > > > Thanks, > > steffn--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Try setting the HTML and BODY elements to the same color -- IIRC that fixed a bug that was similiar; but no guarantees. Best, Thomas Am 26.11.2007 um 18:27 schrieb ftx:> > HI! > > "Good" to hear I am not the only one recognizing this behavior. > > I can only tell you that it is totally reproduceable in Safari 3.0.4 > (523.12) as well as on 2.0.4 (419.3). If I only link the prototype.js > everything is fine again <http://www.fightex.com/test/ > index_noscript.html>. As soon as scriptaculous.js is referenced the > page background gets broken again. As far is i figured out there were > no errors on the javascript console, and I have no idea how to get > more close to the reason why this is happening. If any one more > familiar with the sources of scriptaculous could take a look at this, > it would be really great! > > Cheers, > Steffn > > On Nov 26, 5:51 pm, Phillip Koebbe <phillipkoe...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: >> Hi Steffn >> >> I''m glad you posted this. I noticed the same thing on one of my >> sites >> when I upgraded to Scriptaculous 1.8/Prototype 1.6. I also >> discovered >> that switching tabs is enough to have the background drawn properly. >> I validated my HTML and CSS and decided it was a bug in Safari, so I >> submitted it to Apple. It is odd that it happened with the upgrade >> of >> Scriptaculous/Prototype, but since all other browsers I''ve tried work >> fine, I guessed it was an oddity in Safari that just became apparent >> with the latest js libraries. If you (or someone else) determines >> otherwise, I''d be happy to hear about it. >> >> Peace, >> Phillip >> >> On Nov 26, 3:42 am, ftx <ste...-RbZlAiThDcE@public.gmane.org> wrote:> Hi there! >> >>> I have the following problem and don''t know how to come by this. >>> If I >>> include prototype.js and scriptaculous.js Safari gets a problem with >>> coloring the background of the viewport. It only works where you >>> placed some div, the rest of the page won''t be correctly colored at >>> first. If you resize the window everything is fine. >> >>> I did test this with Safari 2.x/3.x on OS X 10.4.11, other browsers >>> (FF 1.5+, Camino, Opera 9, IE 6+ on Win) are fine with this page. >>> Also >>> confirmed by other Mac Users using various OS X versions and Safari >>> versions. Here you can take a look at the issue <http://www.fightex.com/test >>> > and here you can find a screenshot <http://www.fightex.com/test/scr_safari_scriptaculous_bg_issue.png >>> > >> >>> Scriptaculous Version: 1.8.0 >>> Prototype Version. 1.6.0 >> >>> Thanks, >>> steffn > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
That is, put the following in a style tag or external CSS:
html, body { background-color: black }
Best,
Thomas
Am 26.11.2007 um 18:52 schrieb Thomas Fuchs:
>
> Try setting the HTML and BODY elements to the same color -- IIRC that
> fixed a bug that was similiar; but no guarantees.
>
> Best,
> Thomas
>
> Am 26.11.2007 um 18:27 schrieb ftx:
>
>>
>> HI!
>>
>> "Good" to hear I am not the only one recognizing this
behavior.
>>
>> I can only tell you that it is totally reproduceable in Safari 3.0.4
>> (523.12) as well as on 2.0.4 (419.3). If I only link the prototype.js
>> everything is fine again <http://www.fightex.com/test/
>> index_noscript.html>. As soon as scriptaculous.js is referenced the
>> page background gets broken again. As far is i figured out there were
>> no errors on the javascript console, and I have no idea how to get
>> more close to the reason why this is happening. If any one more
>> familiar with the sources of scriptaculous could take a look at this,
>> it would be really great!
>>
>> Cheers,
>> Steffn
>>
>> On Nov 26, 5:51 pm, Phillip Koebbe
<phillipkoe...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>> Hi Steffn
>>>
>>> I''m glad you posted this. I noticed the same thing on one
of my
>>> sites
>>> when I upgraded to Scriptaculous 1.8/Prototype 1.6. I also
>>> discovered
>>> that switching tabs is enough to have the background drawn
properly.
>>> I validated my HTML and CSS and decided it was a bug in Safari, so
I
>>> submitted it to Apple. It is odd that it happened with the upgrade
>>> of
>>> Scriptaculous/Prototype, but since all other browsers I''ve
tried
>>> work
>>> fine, I guessed it was an oddity in Safari that just became
apparent
>>> with the latest js libraries. If you (or someone else) determines
>>> otherwise, I''d be happy to hear about it.
>>>
>>> Peace,
>>> Phillip
>>>
>>> On Nov 26, 3:42 am, ftx <ste...-RbZlAiThDcE@public.gmane.org>
wrote:> Hi there!
>>>
>>>> I have the following problem and don''t know how to
come by this.
>>>> If I
>>>> include prototype.js and scriptaculous.js Safari gets a problem
>>>> with
>>>> coloring the background of the viewport. It only works where
you
>>>> placed some div, the rest of the page won''t be
correctly colored at
>>>> first. If you resize the window everything is fine.
>>>
>>>> I did test this with Safari 2.x/3.x on OS X 10.4.11, other
browsers
>>>> (FF 1.5+, Camino, Opera 9, IE 6+ on Win) are fine with this
page.
>>>> Also
>>>> confirmed by other Mac Users using various OS X versions and
Safari
>>>> versions. Here you can take a look at the issue
<http://www.fightex.com/test
>>>>> and here you can find a screenshot
<http://www.fightex.com/test/scr_safari_scriptaculous_bg_issue.png
>>>>>
>>>
>>>> Scriptaculous Version: 1.8.0
>>>> Prototype Version. 1.6.0
>>>
>>>> Thanks,
>>>> steffn
>>>
>
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
Thomas,
Thanks for such a quick response! I added a simple
html {
background-color: ccc;
}
and refreshed the page, and the problem is gone. Do you suppose it''s
just a difference in how Safari renders things as opposed to Firefox
and the rest of the pack?
Thanks again!
Phillip
On Nov 26, 2007, at 11:54 AM, Thomas Fuchs wrote:
>
> That is, put the following in a style tag or external CSS:
>
> html, body { background-color: black }
>
> Best,
> Thomas
>
> Am 26.11.2007 um 18:52 schrieb Thomas Fuchs:
>
>>
>> Try setting the HTML and BODY elements to the same color -- IIRC that
>> fixed a bug that was similiar; but no guarantees.
>>
>> Best,
>> Thomas
>>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Spinoffs" group.
To post to this group, send email to
rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
Yeah, it''s just a plain bug... :) Am 26.11.2007 um 19:19 schrieb Phillip Koebbe:> > Thomas, > > Thanks for such a quick response! I added a simple > > html { > background-color: ccc; > } > > and refreshed the page, and the problem is gone. Do you suppose it''s > just a difference in how Safari renders things as opposed to Firefox > and the rest of the pack? > > Thanks again! > Phillip > > On Nov 26, 2007, at 11:54 AM, Thomas Fuchs wrote: > >> >> That is, put the following in a style tag or external CSS: >> >> html, body { background-color: black } >> >> Best, >> Thomas >> >> Am 26.11.2007 um 18:52 schrieb Thomas Fuchs: >> >>> >>> Try setting the HTML and BODY elements to the same color -- IIRC >>> that >>> fixed a bug that was similiar; but no guarantees. >>> >>> Best, >>> Thomas >>> > > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks, great this solves it! But still, why does this only happen if I include the scritpaculous.js and not all the time? Cheers, Steffn On Nov 26, 8:04 pm, Thomas Fuchs <tho...-9D208sng4xU@public.gmane.org> wrote:> Yeah, it''s just a plain bug... :) > > Am 26.11.2007 um 19:19 schrieb Phillip Koebbe: > > > > > Thomas, > > > Thanks for such a quick response! I added a simple > > > html { > > background-color: ccc; > > } > > > and refreshed the page, and the problem is gone. Do you suppose it''s > > just a difference in how Safari renders things as opposed to Firefox > > and the rest of the pack? > > > Thanks again! > > Phillip > > > On Nov 26, 2007, at 11:54 AM, Thomas Fuchs wrote: > > >> That is, put the following in a style tag or external CSS: > > >> html, body { background-color: black } > > >> Best, > >> Thomas > > >> Am 26.11.2007 um 18:52 schrieb Thomas Fuchs: > > >>> Try setting the HTML and BODY elements to the same color -- IIRC > >>> that > >>> fixed a bug that was similiar; but no guarantees. > > >>> Best, > >>> Thomas--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On Nov 26, 7:42 pm, ftx <ste...-RbZlAiThDcE@public.gmane.org> wrote:> Hi there! > > I have the following problem and don''t know how to come by this. If I > include prototype.js and scriptaculous.js Safari gets a problem with > coloring the background of the viewport. It only works where you > placed some div, the rest of the page won''t be correctly colored at > first. If you resize the window everything is fine.I think what you are seeing is a conflict between HTML and XHTML. You pretend that your page is XHTML 1.0 Strict, but it is in fact served as text/html. It is also invalid XHTML - you are missing the closing shortag on the meta element. If you correct the error and serve your page as XHTML, you will get the same result in Firefox and Safari - even if you remove all scripts from the file (but of course you will get nothing in IE, which has no idea what XHTML is). As to why there is a difference between XHTML and HTML, I suggest you ask in news:comp.infosystems.www.authoring.html <URL: http://groups.google.com.au/group/comp.infosystems.www.authoring.html?hl=en&lnk=li>Be prepared to weather some flak for using XHTML at all, but I think you will get the answer. Further, scriptaculous.js loads all the other files, so there is no need to include them all - you are just creating twice the number of script elements as are required. And lastly, the effect you see with HTML and Safari (i.e. if you serve a valid HTML document as HTML rather than invalid XHTML) occurs if you include any script file after prototpye.js - it doesn''t seem to matter what it is, or even if it exists. I don''t have time to track it down any further than that, but I suggest you start by looking at the functions that run when Prototype.js is loaded. -- Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Again, this is just a bug in Safari''s rendering engine... :) Prototype doesn''t "break" Safari, it''s broken to start with... ;) I''d go with the pragmatic fix and telling safari to give a background to the HTML element, too. Btw, solves some rendering bugs in Firefox too, that can happen under specific circumstances. OMG, BROWSERS!!! ;) As for the XHTML 1.0 strict issue -- I recommend using XHTML 1.0 Transitional as the "most compatible" doctype; and serving it as text/ html. These days, that seems to be the way to go: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd "> Best, Thomas Am 27.11.2007 um 13:49 schrieb RobG:> > > > On Nov 26, 7:42 pm, ftx <ste...-RbZlAiThDcE@public.gmane.org> wrote: >> Hi there! >> >> I have the following problem and don''t know how to come by this. If I >> include prototype.js and scriptaculous.js Safari gets a problem with >> coloring the background of the viewport. It only works where you >> placed some div, the rest of the page won''t be correctly colored at >> first. If you resize the window everything is fine. > > I think what you are seeing is a conflict between HTML and XHTML. You > pretend that your page is XHTML 1.0 Strict, but it is in fact served > as text/html. It is also invalid XHTML - you are missing the closing > shortag on the meta element. > > If you correct the error and serve your page as XHTML, you will get > the same result in Firefox and Safari - even if you remove all scripts > from the file (but of course you will get nothing in IE, which has no > idea what XHTML is). > > As to why there is a difference between XHTML and HTML, I suggest you > ask in > > news:comp.infosystems.www.authoring.html > <URL: http://groups.google.com.au/group/comp.infosystems.www.authoring.html?hl=en&lnk=li >> > > Be prepared to weather some flak for using XHTML at all, but I think > you will get the answer. > > Further, scriptaculous.js loads all the other files, so there is no > need to include them all - you are just creating twice the number of > script elements as are required. > > And lastly, the effect you see with HTML and Safari (i.e. if you serve > a valid HTML document as HTML rather than invalid XHTML) occurs if you > include any script file after prototpye.js - it doesn''t seem to matter > what it is, or even if it exists. > > I don''t have time to track it down any further than that, but I > suggest you start by looking at the functions that run when > Prototype.js is loaded. > > > -- > Rob > >--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
On Nov 27, 11:59 pm, Thomas Fuchs <tho...-9D208sng4xU@public.gmane.org> wrote:> Again, this is just a bug in Safari''s rendering engine... :)It may well be, but only if you can support the notion that the HTML body element *must* extend to the full extent of the window (a reference to a W3C recommendation would do). In any case, the document being served by the OP isn''t valid HTML, so all bets are off.> Prototype doesn''t "break" Safari, it''s broken to start with... ;)In the specific example provided by the OP, Safari behaves differently depending on whether Prototype.js and a second script file are included or not. There would seem to be at least an incompatibility relating to Safari and Prototype.js in this case. If Prototype.js doesn''t "break" Safari, then why doesn''t the issue occur with version 1.5 or 1.4? Clearly there is something different in 1.6 that causes the behaviour.> I''d go with > the pragmatic fix and telling safari to give a background to the HTML > element, too.That may "work" for the limited number of browsers that Prototype.js supports, but not only is it invalid HTML (and XHTML), it doesn''t increase anyones understanding of why Safari does what it does. As I pointed out, when the document is served as XHTML, neither Firefox nor Safari extend the body element to the full extent of the window - regardless of whether any script files are loaded or not.> Btw, solves some rendering bugs in Firefox too, that can happen under > specific circumstances. OMG, BROWSERS!!! ;)You are depending on pure coincidence of how browsers handle transition doctypes and invalid markup to fix a problem that you don''t understand (not that I claim to either).> As for the XHTML 1.0 strict issue -- I recommend using XHTML 1.0 > Transitional as the "most compatible" doctype; and serving it as text/ > html. These days, that seems to be the way to go:Which is a really confused recommendation. If you are concerned about web standards, then you should recommend HTML 4.01 strict. It seems a contradiction to use a transitional XHTML doctype served as HTML (which will be treated as invalid HTML by any browser that it is served to) to cause some kind of compatibility in the hope that browsers will all treat the erroneous markup the same. How can you say one browser has a bug because it treats the invalid markup differently to some other browser? This subject is somewhat off topic for this news group, search the archives at comp.infosystems.www.authoring.html to see what others with far more knowledge than I say about the use of XHTML on the web, particularly when served as text/HTML. -- Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to rubyonrails-spinoffs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---