Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #37685 > unrolled thread

Two SUCESSIVE animations on the same element - how?

Back to article view | Back to comp.lang.javascript

Contents

  Two SUCESSIVE animations on the same element - how? groovee@cyberdude.com - 2019-11-03 23:17 -0800
    Re: Two SUCESSIVE animations on the same element - how? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2019-11-04 13:07 -0800
      Re: Two SUCESSIVE animations on the same element - how? groovee@cyberdude.com - 2019-11-06 01:53 -0800
        Re: Two SUCESSIVE animations on the same element - how? "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-11-06 11:47 +0100
          Re: Two SUCESSIVE animations on the same element - how? groovee@cyberdude.com - 2019-11-07 09:07 -0800
            Re: Two SUCESSIVE animations on the same element - how? "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-11-08 00:25 +0100
            Re: Two SUCESSIVE animations on the same element - how? Arno Welzel <usenet@arnowelzel.de> - 2019-11-10 01:11 +0100
              Re: Two SUCESSIVE animations on the same element - how? "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2019-11-11 14:19 +0100
        Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-07 11:00 -0800
          Re: Two SUCESSIVE animations on the same element - how? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2019-11-07 16:46 -0800
            Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-07 22:57 -0800
              Re: Two SUCESSIVE animations on the same element - how? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2019-11-08 04:21 -0800
                Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-08 09:08 -0800
                  Re: Two SUCESSIVE animations on the same element - how? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2019-11-08 10:34 -0800
                    Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-09 01:44 -0800
                      Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-09 02:02 -0800
                        Re: Two SUCESSIVE animations on the same element - how? John G Harris <niam@jghnorth.org.uk.invalid> - 2019-11-09 11:55 +0000
                          Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-09 05:39 -0800
                  Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-09 05:32 -0800
    Re: Two SUCESSIVE animations on the same element - how? groovee@cyberdude.com - 2019-11-09 05:01 -0800
      Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-09 05:45 -0800
        Re: Two SUCESSIVE animations on the same element - how? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2019-11-09 09:12 -0800
          Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-09 13:53 -0800
            Re: Two SUCESSIVE animations on the same element - how? Arno Welzel <usenet@arnowelzel.de> - 2019-11-10 00:55 +0100
              Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-09 19:00 -0800
                Re: Two SUCESSIVE animations on the same element - how? Julio Di Egidio <julio@diegidio.name> - 2019-11-09 21:09 -0800
                  Re: Two SUCESSIVE animations on the same element - how? Arno Welzel <usenet@arnowelzel.de> - 2019-11-10 11:10 +0100
                    Re: Two SUCESSIVE animations on the same element - how? Arno Welzel <usenet@arnowelzel.de> - 2019-11-10 11:29 +0100
                Re: Two SUCESSIVE animations on the same element - how? Arno Welzel <usenet@arnowelzel.de> - 2019-11-10 11:35 +0100
      Re: Two SUCESSIVE animations on the same element - how? "Michael Haufe (TNO)" <tno@thenewobjective.com> - 2019-11-09 09:10 -0800
    Re: Two SUCESSIVE animations on the same element - how? Arno Welzel <usenet@arnowelzel.de> - 2019-11-10 00:51 +0100
      Re: Two SUCESSIVE animations on the same element - how? Arno Welzel <usenet@arnowelzel.de> - 2019-11-10 01:05 +0100
        Re: Two SUCESSIVE animations on the same element - how? Arno Welzel <usenet@arnowelzel.de> - 2019-11-12 12:00 +0100

Page 1 of 2  [1] 2  Next page →

#37685 — Two SUCESSIVE animations on the same element - how?

OK, so say I have a green box on my screen which I want to start off at the top left, move to the top right and THEN from there to the bottom right. How do I do this? (this is just an example).

I have a .goright class with a 

{
   animation-name: goright;
 blah blah

and then a 

@keyframes goright {
  from {
	transform: blah 
  }
  to {
	transform: blah
  }
}



And then, I thought I'd put in ANOTHER:

.godown {
	animation-name: godown;
	blah
}


@keyframes godown {
  from {
	transform: blah
  }
  to {
	transform: blah
  }
}




And then put in this in my JS code:


	greenbox.className =  "goright";
        greenbox.className =  "godown" ;



But this is not working! - The box will go to the right and then JUMP BACK TO WHERE IT CAME FROM! Why??!! What am I supposed to do now??


Thanks for your help.

[toc] | [next] | [standalone]

#37689

On Monday, November 4, 2019 at 1:18:00 AM UTC-6, gro...@cyberdude.com wrote:
> OK, so say I have a green box on my screen which I want to start off at the top left, move to the top right and THEN from there to the bottom right. How do I do this? (this is just an example).
> 
> I have a .goright class with a 
> 
> {
>    animation-name: goright;
>  blah blah
> 
> and then a 
> 
> @keyframes goright {
>   from {
> 	transform: blah 
>   }
>   to {
> 	transform: blah
>   }
> }
> 
> 
> 
> And then, I thought I'd put in ANOTHER:
> 
> .godown {
> 	animation-name: godown;
> 	blah
> }
> 
> 
> @keyframes godown {
>   from {
> 	transform: blah
>   }
>   to {
> 	transform: blah
>   }
> }
> 
> 
> 
> 
> And then put in this in my JS code:
> 
> 
> 	greenbox.className =  "goright";
>         greenbox.className =  "godown" ;
> 
> 
> 
> But this is not working! - The box will go to the right and then JUMP BACK TO WHERE IT CAME FROM! Why??!! What am I supposed to do now??
> 
> 
> Thanks for your help.

You should use `animation-fill-mode: forwards;`

Ref:

<https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Animations/Using_CSS_animations>

Example:
<https://codepen.io/mlhaufe/pen/MWWQBgx>

[toc] | [prev] | [next] | [standalone]

#37700

On Tuesday, 5 November 2019 02:37:44 UTC+5:30, Michael Haufe (TNO)  wrote:

> You should use `animation-fill-mode: forwards;`
> 
> Ref:
> 
> <https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Animations/Using_CSS_animations>
> 
> Example:
> <https://codepen.io/mlhaufe/pen/MWWQBgx>


Er - in that Codepen, when I click "Go Right", it goes right, but then when I click "Go Down" it SNAPS BACK TO THE LEFT before going down, instead of going down FROM the right!! :)

[toc] | [prev] | [next] | [standalone]

#37701

groovee@cyberdude.com wrote on 06 Nov 2019 in comp.lang.javascript:

> On Tuesday, 5 November 2019 02:37:44 UTC+5:30, Michael Haufe (TNO) 
> wrote: 
> 
>> You should use `animation-fill-mode: forwards;`
>> 
>> Ref:
>> 
>> <https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Animations/Using_C
>> SS_animations> 
>> 
>> Example:
>> <https://codepen.io/mlhaufe/pen/MWWQBgx>
> 
> 
> Er - in that Codepen, when I click "Go Right", it goes right, but then
> when I click "Go Down" it SNAPS BACK TO THE LEFT before going down,
> instead of going down FROM the right!! :) 

Just give the second class it's own starting coordinates.



-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#37703

On Wednesday, 6 November 2019 16:18:05 UTC+5:30, Evertjan.  wrote:

> Just give the second class it's own starting coordinates.
> 


As I said, this is just an example - there could be MANY situations where I need to know how to pull off this kind of thing where "giving the second class it's own starting coordinates" will Not Be An Option. In any case, that's not the point  - why WILL what I posted not work?

[toc] | [prev] | [next] | [standalone]

#37705

groovee@cyberdude.com wrote on 07 Nov 2019 in comp.lang.javascript:

> On Wednesday, 6 November 2019 16:18:05 UTC+5:30, Evertjan.  wrote:
> 
>> Just give the second class it's own starting coordinates.
>> 
> 
> 
> As I said, this is just an example - there could be MANY situations
> where I need to know how to pull off this kind of thing where "giving
> the second class it's own starting coordinates" will Not Be An Option.
> In any case, that's not the point  - why WILL what I posted not work? 

You are the programmer, you can find out the end position and manipulate the 
class to use that as the new starting position.

If you want to use a CSS only solution, you are in the wrong NG.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#37741

groovee@cyberdude.com:

> On Wednesday, 6 November 2019 16:18:05 UTC+5:30, Evertjan.  wrote:
> 
>> Just give the second class it's own starting coordinates.
>> 
> 
> 
> As I said, this is just an example - there could be MANY situations
> where I need to know how to pull off this kind of thing where "giving
> the second class it's own starting coordinates" will Not Be An
> Option. In any case, that's not the point  - why WILL what I posted
> not work?

1) You just set the class "goright" and then immediately afterwards to
"godown" - but you have to wait until the first animation is finished
before you change the class. This can be done by adding an event
listener for the 'animationend' and checking which class is currently set.

2) The animations don't run only once, because you did not specify
"animation-fill-mode: forwards;" in the CSS class.

My example for this: https://arnowelzel.de/samples/animation2.html




-- 
Arno Welzel
https://arnowelzel.de

[toc] | [prev] | [next] | [standalone]

#37750

Arno Welzel <usenet@arnowelzel.de> wrote on 10 Nov 2019 in 
comp.lang.javascript:

> My example for this: https://arnowelzel.de/samples/animation2.html

Experimenting with this:

<http://hannivoort.org/test/cssMove.html>

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#37704

On Wednesday, 6 November 2019 10:53:29 UTC+1, gro...@cyberdude.com  wrote:
> On Tuesday, 5 November 2019 02:37:44 UTC+5:30, Michael Haufe (TNO)  wrote:
<snip>
> > <https://codepen.io/mlhaufe/pen/MWWQBgx>
> 
> Er - in that Codepen, when I click "Go Right", it goes right, but then when I click "Go Down" it SNAPS BACK TO THE LEFT before going down, instead of going down FROM the right!! :)

I have simplified and fixed few issues in Michael's example: now it runs even
on Edge: <https://codepen.io/jp-diegidio/pen/NWWMeKO>

HTH,

Julio

[toc] | [prev] | [next] | [standalone]

#37706

On Thursday, November 7, 2019 at 1:00:45 PM UTC-6, Julio Di Egidio wrote:
> On Wednesday, 6 November 2019 10:53:29 UTC+1, gro...@cyberdude.com  wrote:
> > On Tuesday, 5 November 2019 02:37:44 UTC+5:30, Michael Haufe (TNO)  wrote:
> <snip>
> > > <https://codepen.io/mlhaufe/pen/MWWQBgx>
> > 
> > Er - in that Codepen, when I click "Go Right", it goes right, but then when I click "Go Down" it SNAPS BACK TO THE LEFT before going down, instead of going down FROM the right!! :)
> 
> I have simplified and fixed few issues in Michael's example: now it runs even
> on Edge: <https://codepen.io/jp-diegidio/pen/NWWMeKO>


Your "simplification" doesn't compose classes as the OP asked. Good job incorrecting me, try again.

[toc] | [prev] | [next] | [standalone]

#37708

On Friday, 8 November 2019 01:46:19 UTC+1, Michael Haufe (TNO)  wrote:
> On Thursday, November 7, 2019 at 1:00:45 PM UTC-6, Julio Di Egidio wrote:
> > On Wednesday, 6 November 2019 10:53:29 UTC+1, gro...@cyberdude.com  wrote:
> > > On Tuesday, 5 November 2019 02:37:44 UTC+5:30, Michael Haufe (TNO)  wrote:
> > <snip>
> > > > <https://codepen.io/mlhaufe/pen/MWWQBgx>
> > > 
> > > Er - in that Codepen, when I click "Go Right", it goes right, but then when I click "Go Down" it SNAPS BACK TO THE LEFT before going down, instead of going down FROM the right!! :)
> > 
> > I have simplified and fixed few issues in Michael's example: now it runs even
> > on Edge: <https://codepen.io/jp-diegidio/pen/NWWMeKO>
> 
> Your "simplification" doesn't compose classes as the OP asked. Good job
> incorrecting me, try again.

I wasn't correcting you, I couldn't care less.

That said, you are simply incompetent: the job (the developer's job) is not
to do what the OP is trying to do as he is trying to do it, the job is to
**implement a requirement**, which in this case was "the box from here to
there to there, and then how do I keep going without reloading the page??"

Not to mention, your little example was indeed 20 problems in 10 lines,
maybe you normally use a transpiler.

Way to go...

Julio

[toc] | [prev] | [next] | [standalone]

#37721

On Friday, November 8, 2019 at 12:58:06 AM UTC-6, Julio Di Egidio wrote:
> On Friday, 8 November 2019 01:46:19 UTC+1, Michael Haufe (TNO)  wrote:
> > [...]
> > 
> > Your "simplification" doesn't compose classes as the OP asked. Good job
> > incorrecting me, try again.
> 
> I wasn't correcting you, I couldn't care less.
> 
> That said, you are simply incompetent: the job (the developer's job) is not
> to do what the OP is trying to do as he is trying to do it, the job is to
> **implement a requirement**, which in this case was "the box from here to
> there to there, and then how do I keep going without reloading the page??"

When you make up requirements for the OP, of course it's easy to say you've accomplished something. No one said anything about reloading the page. 

> Not to mention, your little example was indeed 20 problems in 10 lines,
> maybe you normally use a transpiler.
> 
> Way to go...

Not capable of discerning intent from a pen eh? If you want to go down that route fine: why would you foolishly animate a margin and not compose classes? Way to go...

[toc] | [prev] | [next] | [standalone]

#37724

On Friday, 8 November 2019 13:21:09 UTC+1, Michael Haufe (TNO)  wrote:
> On Friday, November 8, 2019 at 12:58:06 AM UTC-6, Julio Di Egidio wrote:
> > On Friday, 8 November 2019 01:46:19 UTC+1, Michael Haufe (TNO)  wrote:
> > > [...]
> > > 
> > > Your "simplification" doesn't compose classes as the OP asked. Good job
> > > incorrecting me, try again.
> > 
> > I wasn't correcting you, I couldn't care less.
> > 
> > That said, you are simply incompetent: the job (the developer's job) is not
> > to do what the OP is trying to do as he is trying to do it, the job is to
> > **implement a requirement**, which in this case was "the box from here to
> > there to there, and then how do I keep going without reloading the page??"
> 
> When you make up requirements for the OP,

This was the opening paragraph:

"OK, so say I have a green box on my screen which I want to start off at the top
left, move to the top right and THEN from there to the bottom right. How do I do
this? (this is just an example)."

Are you trying to tell me that you cannot even read or do you actually disagree
that is the requirement?

Regardless, I am going to give your code a more thorough review later, as you
insist and for your reference...

Julio

> of course it's easy to say you've accomplished something. No one said anything about reloading the page. 
> 
> > Not to mention, your little example was indeed 20 problems in 10 lines,
> > maybe you normally use a transpiler.
> > 
> > Way to go...
> 
> Not capable of discerning intent from a pen eh? If you want to go down that route fine: why would you foolishly animate a margin and not compose classes? Way to go...

[toc] | [prev] | [next] | [standalone]

#37725

On Friday, November 8, 2019 at 11:08:46 AM UTC-6, Julio Di Egidio wrote:
> [...]
>
> This was the opening paragraph:
> 
> "OK, so say I have a green box on my screen which I want to start off at the top
> left, move to the top right and THEN from there to the bottom right. How do I do
> this? (this is just an example)."
> 
> Are you trying to tell me that you cannot even read or do you actually disagree
> that is the requirement?

Unlike you, I read more than the first paragraph which included important details. Do try to keep up...
 
> Regardless, I am going to give your code a more thorough review later, as you
> insist and for your reference...

Maybe you should finish the homework I already assigned you first? You may find redemption in it:

<https://groups.google.com/d/msg/comp.lang.javascript/9FxKCWG7NLQ/iXVPdwuaCgAJ>

But hey, if you want to "review" every back-of-napkin snippet I create go ahead, I have plenty. Know that this would amount to little more than mental masturbation though; I've yet to be informed by anything you've said and the first piece of code you've written in this group in god knows how long misses the mark as well as the point.

[toc] | [prev] | [next] | [standalone]

#37728

On Friday, 8 November 2019 19:34:13 UTC+1, Michael Haufe (TNO)  wrote:
> On Friday, November 8, 2019 at 11:08:46 AM UTC-6, Julio Di Egidio wrote:
> > [...]
> >
> > This was the opening paragraph:
> > 
> > "OK, so say I have a green box on my screen which I want to start off at the top
> > left, move to the top right and THEN from there to the bottom right. How do I do
> > this? (this is just an example)."
> > 
> > Are you trying to tell me that you cannot even read or do you actually disagree
> > that is the requirement?
> 
> Unlike you, I read more than the first paragraph which included important
> details. Do try to keep up...

Which I take to mean "the latter".  You are totally in denial, the OP has
even come back to you as well as to Evertroll complaining that you guys
weren't solving the problem.  But that's just to point out your delusion,
because I certainly don't need to defend problem vs solution, or requirements
vs implementations, that's the fucking 101 of the discipline and you simply
have no clue.

> > Regardless, I am going to give your code a more thorough review later, as you
> > insist and for your reference...
> 
> Maybe you should finish the homework I already assigned you first? You may
> find redemption in it:
> <https://groups.google.com/d/msg/comp.lang.javascript/9FxKCWG7NLQ/iXVPdwuaCgAJ>

That BULLSHIT about what YOU think is functional: a switch statement, LOL!!
After in fact giving you SEVERAL replies to just get back more and more denial.
You are incompetent AND delusional, and that IS my answer.

> But hey, if you want to "review" every back-of-napkin snippet I create go
> ahead

You wish...

EOD.

Julio

[toc] | [prev] | [next] | [standalone]

#37729

On Saturday, 9 November 2019 10:44:07 UTC+1, Julio Di Egidio  wrote:
> On Friday, 8 November 2019 19:34:13 UTC+1, Michael Haufe (TNO)  wrote:

> > Maybe you should finish the homework I already assigned you first? You may
> > find redemption in it:
> > <https://groups.google.com/d/msg/comp.lang.javascript/9FxKCWG7NLQ/iXVPdwuaCgAJ>
> 
> That BULLSHIT about what YOU think is functional: a switch statement, LOL!!
> After in fact giving you SEVERAL replies to just get back more and more denial.
> You are incompetent AND delusional, and that IS my answer.

P.S.
For the chronicle, OOP uber alles is a plain fraud, just like the foundational
fraud of fake agility, that "agile vs waterfall": what THEY claim was the state
of the art...  Let's hope those bloody scammers and vile cunts go fry in hell.

So much for the grandeur of our theme: have a wonderful day.

Julio

[toc] | [prev] | [next] | [standalone]

#37730

On Sat, 9 Nov 2019 02:02:47 -0800 (PST), Julio Di Egidio
<julio@diegidio.name> wrote:

  <snip>
>For the chronicle, OOP uber alles is a plain fraud, 
  <snip>

Is it OO *Programming* or OO *Design* that you criticise? Certainly
OOD suffers from a lot of hype and extremism. People who don't really
know what they're doing are encouraged to go mad and describe
everything as an object.

  John

[toc] | [prev] | [next] | [standalone]

#37733

On Saturday, 9 November 2019 12:55:22 UTC+1, John G Harris  wrote:
> On Sat, 9 Nov 2019 02:02:47 -0800 (PST), Julio Di Egidio
> <julio@diegidio.name> wrote:
> 
>   <snip>
> >For the chronicle, OOP uber alles is a plain fraud, 
>   <snip>
> 
> Is it OO *Programming* or OO *Design* that you criticise? Certainly
> OOD suffers from a lot of hype and extremism. People who don't really
> know what they're doing are encouraged to go mad and describe
> everything as an object.

Sorry, just a slip, I meant the infamous OO uber alles, which of course is
about the whole paradigm, not about this or that particular construct (and
you forget analysis, OOA: and who could blame you, since analysis has been
literally and purposely obliterated from the panorama top begin with, in
order to open the doors to that ungodly nonsense called vendor-driven
development? Of software, courses certificates, books, conferences, and
what not, including *necessarily* broken development paradigms...).

In fact, *most* systems/programs are objectively *very* simple, so it
doesn't even matter much what you use as long as you use it with criterion:
just keep it *clean and readable*, these are real and immediate musts and
the true learning curve...

Julio

[toc] | [prev] | [next] | [standalone]

#37732

On Friday, 8 November 2019 18:08:46 UTC+1, Julio Di Egidio  wrote:
> On Friday, 8 November 2019 13:21:09 UTC+1, Michael Haufe (TNO)  wrote:
> > On Friday, November 8, 2019 at 12:58:06 AM UTC-6, Julio Di Egidio wrote:
> > > On Friday, 8 November 2019 01:46:19 UTC+1, Michael Haufe (TNO)  wrote:
> > > > [...]
> > > > 
> > > > Your "simplification" doesn't compose classes as the OP asked. Good job
> > > > incorrecting me, try again.
> > > 
> > > I wasn't correcting you, I couldn't care less.
> > > 
> > > That said, you are simply incompetent: the job (the developer's job) is not
> > > to do what the OP is trying to do as he is trying to do it, the job is to
> > > **implement a requirement**, which in this case was "the box from here to
> > > there to there, and then how do I keep going without reloading the page??"
> > 
> > When you make up requirements for the OP,
> 
> This was the opening paragraph:
> 
> "OK, so say I have a green box on my screen which I want to start off at the top
> left, move to the top right and THEN from there to the bottom right. How do I do
> this? (this is just an example)."
> 
> Are you trying to tell me that you cannot even read or do you actually
> disagree that is the requirement?
> 
> Regardless, I am going to give your code a more thorough review later, as you
> insist and for your reference...

A promise is a promise, right?

Overall:
1. I was actually being collaborative, at least that was the intention: to
   restart from the few lines of code you had sketched and just complete it.
   Also few days had passed so I thought you were just not interested.  And
   I did have my qualms with your code, but I was quite careful not to bring
   any of those up.  Yet, you just take it as a personal attack.
2. You cannot read: see above and up-thread.
3. Your "solution" is an utter mess, which I'll put briefly as follows:

Botched requirements:
    Explicit: The OP's requirements:
    - Move the box as requested (and even if you interpret it as two separate
      events, to which I have in fact never objected, you still have botched
      both the control logic as well as the plain trajectory).
    Explicit (meta): The "example" (you brought this up, remember):
    - Closedness: RESET! It's about being able to *operate* it.
      (Have you played with your example at least to test it?  Wasn't it
      annoying already to you that you had to reload the page?)
    - Cogency: no tech complications outside the scope, you introduce semantic
      html, CSS functions, and your JS was the least problematic part, except
      that even there you could not just write var qs = document.querySelector:
      smart in the wrong direction...
    Implicit (aka technical as opposed to functional requirements):
    - Browser support, or write on top "Google Chrome only" or whatever it is.
Ugly implementation (well, IMO):
    - Absolutely positioned and dimensioned CSS?  Bah...

That is what I'd more or less point out in a technical review, which I offer
to you if you like and to the public for reference.

That said, you have exhausted your free allowance: from this point and unless
you change your attitude, I'll be dealing with you as with any other nut case
with some agenda.

HTH,

Julio

[toc] | [prev] | [next] | [standalone]

#37731

Guys, Please Stop Fighting!

This *particular example* is not the important thing here, but rather the larger question of *how to apply 2 different classes successively*. Julio, thanks for your help, but putting a "50%" in the keyframes is Not what I'm looking for, at all.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.javascript

csiph-web