Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

How can I print a webpage without all the link's URLs appearing throughout the page?

  • 4 답장
  • 5 이 문제를 만남
  • 118 보기
  • 최종 답변자: bulla

more options

A long time ago I think I changed my Firefox settings so that when I print a web page, all the links on that that page get printed with their often l-o-n-g URLs. Some pages are really hard to read with about 8 long URLs all over the page.

I've googled around on how to change it, but haven't had any luck.

Can anybody help?

Thanks :-)

A long time ago I think I changed my Firefox settings so that when I print a web page, all the links on that that page get printed with their often l-o-n-g URLs. Some pages are really hard to read with about 8 long URLs all over the page. I've googled around on how to change it, but haven't had any luck. Can anybody help? Thanks :-)

선택된 해결법

Thanks Oxylatium, for replying.

I've concluded that there's something wrong with the page, because

- My firefox doesn't have this problem with other pages I've tested out - the actual PAGE has this problem in Google Chrome browser. So given that it's a problem with 2 browsers, I've decided that I'll put up with it.

thanks again  :-)

문맥에 따라 이 답변을 읽어주세요 👍 0

모든 댓글 (4)

more options

Do you speak about the URL of the webpage displayed in the header of the print output?

more options

No - the links are appearing throughout the page and document.

Sorry about the quality of the photo. Hopefully you'll be able to see this example - the other pages are very similar.

The links are appearing all through the page. Near the top of the page, and about 4 times near the bottom of the page

What setting do I change? Thanks  :-)

글쓴이 bulla 수정일시

more options

do you have an URL to test?

more options

선택된 해결법

Thanks Oxylatium, for replying.

I've concluded that there's something wrong with the page, because

- My firefox doesn't have this problem with other pages I've tested out - the actual PAGE has this problem in Google Chrome browser. So given that it's a problem with 2 browsers, I've decided that I'll put up with it.

thanks again  :-)