Closed Bug 164853 Opened 22 years ago Closed 22 years ago

Some errors in interpreting stylesheets (and others

Categories

(Core :: DOM: HTML Parser, defect)

Product:
Core
Component:
DOM: HTML Parser
Platform:
x86
Windows NT
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 127642

People

(Reporter: stabilo_boss, Assigned: harishd)

References

(
URL
)

Details

Attachments

(1 file)

screen shot
70.43 KB, image/jpeg
Details 
an image is worth 100 words... so see by yourself.
This page may be complex, but that happened too on more simple pages (ignoring
some  embedded style sheets instructions.)

That bug happended with version 1.0 too

Hope it helps. keep up the _EXCELLENT_ work !
Attached image screen shot — 

    
    

    
  
Which particular instructions got ignored here?

    
    

    
  
It seem from the snapshot that the reporter was stating that the texts is
overlapping the images.  I'll see if I can create a testcase for that and see
what happen.  Would need to filter the scripting to make sure it is not an
invalid script.  But I have to go out for lunch first.

    
    

    
  
I noticed the images are swapping, interesting!  The problem lie with the pop-up
menu.  Will need to strip down the code which I'm going to do right now.  Give
me one day to create a testcase for this.

Status --> New
Status: UNCONFIRMED → NEW
Ever confirmed: true

    
    

    
  
I have decided to stop for now and not do the testcase.  If anyone want to
volunteer for this, then go ahead!

I have been breaking down the code and I missed one code somewhere that is
needed to make this work.

We got to give the WebMaster of that website some credit.  The scripting is
heavy in "<DIV>", tables, javascript, javascript version detection, browser
detection, etc.  The WebMaster probably just hung himself when s/he saw more
hunting task to make this website be compactible with Mozilla.  Mozilla just
doesn't follow the scripting too well so lots of things look broken on that
website.  We know the table layout have problem so it is still an unfinished
business with Mozilla.  Once Mozilla continue to improve, then we'll have an
easier time to narrow down the problem.

I found one interesting observation.  When I remove this line of code,
"<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">" then most of hte
feature on the website fixed itself but not all of it.

I'm now moving on to do more bug squashing and patching.

    
    

    
  
So this is only a problem in standards mode?  In a debug build, I get the
following assertion from the page:

###!!! ASSERTION: all the skipped content tokens did not get handled:
'mSkippedContent.GetSize() == 0', file CNavDTD.cpp, line 896
Break: at file CNavDTD.cpp, line 896

Over to parser.
Assignee: karnaze → harishd
Component: HTMLTables → Parser
QA Contact: amar → moied

    
    

    
  
Well, I used the nightly build.  Is this a debug build?

    
    

    
  
Nightlys are not debug builds, no... You'd know if you were runnign a debug
build -- it's about 5 time slower, spits lots of stuff to the console, and the
binary is about 4 times as big.

    
    

    
  
From the Mozillazine forums
<http://www.mozillazine.org/forums/viewtopic.php?t=6149> (and after looking at
the site), it seems ok now.

    
    

    
  
site has since changed to remove the doctype.

is there still an issue that needs investigating here, or can this be marked as
a dupe of the tech evang bug on this site (bug 127642)?

    
    

    
  
Assertions are always an issue that should be investigated.

    
    

    
  
got some people on IRC to check the page, with and without the doctype. without
the doctype things are fine (except for a bogus CSS property called
"layer-background-color").

putting the strict doctype back in, you get two CSS errors and:
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
c:/mozilla/tree2/mozilla/layout/html/base/src/nsFrame.cpp, line 2577
but apparently that's a known issue. no sign of the assertion mentioned in
comment 6.

so no mozilla bug with or without the doctype, and the fixed site is ok now
they've removed the doctype, so I think we're good. hope that's enough
investigation :)


*** This bug has been marked as a duplicate of 127642 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE

          You need to log in
          before you can comment on or make changes to this bug.
        






  

    
  







  

    

      
Attachment

      

      
      
      
      
    

    

      

        

          

            
General

            

              Creator: 



            

            
Created: 

            
Updated: 

            
Size: