p4ulypops / jquery-clean

Automatically exported from code.google.com/p/jquery-clean
0 stars 0 forks source link

Changes - tagIgnore #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,

its working fine, is it possible to make by default all tags in "tagIgnore"
allow selected tags ?

Thanks
KS

Original issue reported on code.google.com by shari...@gmail.com on 3 Apr 2010 at 9:33

GoogleCodeExporter commented 9 years ago
Hi KS,

Sorry, but I'm not sure what you mean, can you explain and perhaps illustrate 
this?

Ant

Original comment by antixsof...@gmail.com on 4 Apr 2010 at 6:13

GoogleCodeExporter commented 9 years ago
Just realised that tagIgnore has been superseded by removeTags.
As this was an internal field anyway, I have removed it and placed the contents 
as
the default for removeTags.

Is this what you meant?

its in 1.2.1 on the trunk, please have a look

Original comment by antixsof...@gmail.com on 4 Apr 2010 at 6:49

GoogleCodeExporter commented 9 years ago
Hi Ant,

Thanks for responding, n sorry for my short message. What I was suggesting, 
instead
of number of tags listing in tagIgnore; why not have all the tags by default 
consider
as Ignore or removed tags and allow only tags mentioned in other functioning 
tags
like inline,tagRequiredParent,tagProtect,tagSelfClosing etc.. or considering a 
new
variable with allowed tags. So far, number of tags I've seen is about 120 
including
tags from HTML5 and I think adding those tags in tagIgnore will make a big list 
and
size of script also high.

Regards

KS

Original comment by shari...@gmail.com on 5 Apr 2010 at 12:46

GoogleCodeExporter commented 9 years ago
Hi KS,

I understand, but there are some tags which are not mentioned in those lists, 
and
they fall into the not inline, allow nesting and empty, not requiring a parent, 
not
protected, closing and have class as their only attribute.

The point is, that I only mention the ones that require some kind of special
treatment, hopefully meaning the rest are treated the same.

I take your point too, and should a different approach, which results in a 
smaller
code footprint is needed for HTML5 support I will remember your suggestion.

I'm not sure when I will wade into HTML5 support, perhaps at the end of my 
current
contract in 3 months or so.

Thanks for all you input anyway, hope the code is ok for your purposes for now, 
if
not please do raise another request.

All the best, Ant

Original comment by antixsof...@gmail.com on 6 Apr 2010 at 6:41

GoogleCodeExporter commented 9 years ago
Ant,

For now the script is okay, will wait for any changes in future.

Thanks and I really appreciate for your support, for both HTMLClean and 
HTMLInput
updates (jquery UI 1.8 support)

Thanks again,

KS

Original comment by shari...@gmail.com on 6 Apr 2010 at 8:38