Interview Questions for Javascript Problems [closed]

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetor开发者_StackOverflow社区ical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 12 years ago.

"What is the most difficult problem you faced in web designing (javascript or css related) and how did you debug and solved it?"

This is the question asked to me in an interview. According to my experience I answered it but interviewer expected some more advanced answer from me. Could you pls share with me the problems which you faced and how did you able to solve it?

Thanks

---

Continue to maintain sites for IE6

---

What is the most difficult problem you faced in web designing (javascript or css related) and how did you debug and solved it?

You see the point I'm making? Not that asking this question is wrong. I would ask it for perspective and to get me thinking about my experience. ("Oh, yeah. I did something like that once.") However, it seems that you want to substitute the experience of someone else for your own. Unless the interviewer doesn't know what they're doing, they'll see through it.

Edit: Specifically, I would only ask people to tell me the types of problems they've solved.

Edit2: Then, I'd try to recreate and solve them on my own, if possible.

Edit3: The only thing that comes to mind ATM, is wrapping my head around just what 'this' means in JavaScript.

I also ran into a hairy issue using jQuery to create a tabbed interface. The close tab icon (an 'X' icon) kept moving around, seemingly at random. This was also a lot JavaScript event hell. (The situation where the meaning of 'this' is very important for the structure of the code.)

---

If you look around here for javascript questions, you will see the difficult problems people faced and often see how those problems were solved.

For myself, the most difficult thing I have done in javascript is paginate a large web page into many small ones to appear as a book. I solved it with lots of research and asking a few questions on SO.

---

what I meet was consequential loading/saving data from/to web services, calls to which you now are async, we were to introduce an layer receiving all async callbacks and making consequental calls

---

Biggest JS problem? Having to deal with existing code.

I have pity for those who have to maintain crappy scripts on a daily basis and can hardly blame front end developers and webdesigners for what appears as a reflex: "Uuh! Let's do it from scratch" :)