Re: Various DOM-related wrappers (Code Worth Recommending Project)

On Dec 9, 12:45 pm, Peter Michaux <petermich...@xxxxxxxxx> wrote:
On Dec 9, 9:13 am, David Mark <dmark.cins...@xxxxxxxxx> wrote:

On Dec 9, 11:20 am, Peter Michaux <petermich...@xxxxxxxxx> wrote:

On Dec 9, 4:32 am, David Mark <dmark.cins...@xxxxxxxxx> wrote:

On Dec 9, 12:02 am, Peter Michaux <petermich...@xxxxxxxxx> wrote:

[snip]

I realize that the task of finalizing, adding and documenting each is
a bottleneck,

Yes. I am working on an automated testing system now and that will

That's interesting. How will that work?

The interesting part is that the testing framework needs to limit how
much client side scripting is used as it is testing a client side
scripting library. This is so even very old browsers can be tested.

I'm using a series of communications between the client and server.
The server orchestrates everything with a series redirects from test
page to test page using redirects until all test pages have been run.

The client logs test assertions (pass and fail) to the server by
setting (new Image()).src since this is the oldest(?) way to
communicate with the server. There will be extremely old browsers that
can't do this and those browsers will require manual testing if they
are to be tested at all.

The only other requirement is that the browser can set
window.location.

I think this is the ultimate in a low tech automated system for
testing.

Sounds good to me. I have always tested manually and it is time-
consuming.

[snip]


What I'm trying to do is focus which lower level functionality goes in
first. Lower level functionality that is required by the higher level
modules should have priority. The lower level functionality
prerequisite to a particular module will necessarily be included
before or at the time the higher level module is included.

Right. I am basing my recommendations for the initial low-level
functionality based on what is used by my higher-level modules.

[snip]


I no longer think that is even possible and window.onload is the only
option.

<URL:http://peter.michaux.ca/article/553>

It is impossible to exactly simulate DOMContentLoaded, but that has
never been a goal of mine. I simple stopped using onload by itself
(it is used as a fallback for situations when the DOMContentLoaded
event or simulation fails to work.) In a nutshell, a timeout set at
the bottom of the page calls the listener (and this is always optional
as onload used as a fallback.) As long as a page degrades gracefully
without script, then the split second that the content is visible
without enhancement is not an issue. In cases where the layout
changes dramatically on enhancement, I add style rules to hide certain
content during the page load.

[snip]


I can't keep up on more than is going on right now. I didn't think

This automated testing suite should help that. But if only one person
is handling documentation and everybody else is adding and
scrutinizing code, then a bottleneck will always exist.

think this project would be so popular!

It will certainly fill a glaring need once the basic foundation is in
place. After that, I'm sure the popularity will increase
exponentially.
.

Relevant Pages

  • RE: Linux VPN (again)
    ... >> replies too which the answer was yes, windows clients will work with a ... >> linux vpn server. ... > into the client so you don't have to deal with it. ...
    (Security-Basics)
  • RE: It takes two to tango
    ... [SNIP] ... > If the client was not notified, after the vulnerability was published (not ... > the exploit), businesses affected by the security hole, could sue the ... the potential cost of producing/shipping these plastic pieces. ...
    (Vuln-Dev)
  • [Full-Disclosure] RE: It takes two to tango
    ... [SNIP] ... > If the client was not notified, after the vulnerability was published (not ... > the exploit), businesses affected by the security hole, could sue the ... the potential cost of producing/shipping these plastic pieces. ...
    (Full-Disclosure)
  • Re: Various DOM-related wrappers (Code Worth Recommending Project)
    ... much client side scripting is used as it is testing a client side ... Testing has higher priority than documentation. ... I think the items related to feature detection ... Lower level functionality that is required by the higher level ...
    (comp.lang.javascript)
  • Re: META redirect
    ... Most sites serve images, too, or use CSS, but they are just as optional as client-side scripting. ... However, the XMLHTTP object is provided by ActiveX, so even that limited action will necessitate the design and implementation of a system that will undergo graceful degradation if the author intends to use that increasingly popular feature. ... you seem to have assumed that a user explicitly disabling scripting is the only concern. ...
    (comp.infosystems.www.authoring.html)