Set View Source font family and size

UNCONFIRMED
Unassigned

Status

()

--
enhancement
UNCONFIRMED
18 years ago
9 years ago

People

(Reporter: aha, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

18 years ago
In preferences could be possibility to set font for View Source page (size,
font-face). 

Common monotype font is good for displaying in page, but for example size in
View     Source could be smaller. In menus of View Source exist function for
percentual resize of view, but you have to set it everytime you viewing page source.

I added related 'remember text size in View Source mode' feature as 
http://bugzilla.mozilla.org/show_bug.cgi?id=88534
but that was marked as Resolved/Invalid .

Comment 1

18 years ago
This seems reasonable to be able to change source font family and size. :-)

Note right now you have to change (view...text size...) in every page source window.

Not sure if the componenet should be in preferences though?

Marking new.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: [RFE] possibility to set View Source font → [RFE] Set View Source font family and size

Comment 2

18 years ago
I'm adding gerv to cc list (i remember he did the source syntex highlighting). 
Sorry if wrong.
Nope - wasn't me :-) I think it was Doron.

Gerv
->doronr, since samir's away on sabbatical.
Assignee: sgehani → doronr

Comment 5

18 years ago
We probably need special prefs for viewsource only. Text Size and Font Famile
sounds good.

Since I am on vacation too, futured.  Possible UI changes to prefs, cc: mpt/blake.
Target Milestone: --- → Future
Actually...  I would recommend a single pref.  Size.  As a percentage of the
default monospace font size.  There is no reason to use any font-family other
than monospace for source.

I guess we could read that pref in viewsource.js and insert it into the
stylesheet that handles viewsource...  thoughts?

Comment 7

18 years ago
good idea, i doubt one would need a non-monospace font.
(Reporter)

Comment 8

18 years ago
"a percentage of the default monospace font size." - Percentage is any 
typographic unit?! 

Please, allow to users specify real font-size, not something, that have to be 
recounted and rounded... If default Monospace font will be 12 points, so for 13 
points font size in View Source you have to enter 108,3333333333% and for 11 
points in View Souce you have to enter 91,6666666. Really good idea =)

"One monospace font-family ought to be enough for anyone." - doesn't sound it 
similar to anything? =)
> "One monospace font-family ought to be enough for anyone." - doesn't sound it
> similar to anything? =)

It does, actually.  Similar to the CSS spec.

Adam, what I proposed was basically remembering the zoom level you've set in
view source, I guess.  As for "any typographic unit":

1)  Current font preferences only allow "px", not "pt" or other units. This is
    for a reason -- the UI is much simpler this way.
2)  We could certainly have a way to set this size and this font to any font
    family and any size in any of the CSS units.  The problem is finding space
    for this UI!  Preferences are overcrowded already.

Hence my suggestion of just remembering the zoom percentage....
Oh.  One more thing.  You can style the viewsource content using userContent.css

viewsource.css has:

.viewsource {
  font-family: -moz-fixed;
  font-weight: normal;
  font-size: normal;
  color: black;
  white-space: pre;
}

So in userContent.css you can just add:

.viewsource {
  font-family: "My favorite font" !important;
  font-size: 9px !important;
}

Comment 11

18 years ago
I really don't see the point here. Are we going to end up with separate prefs 
for the default font used in Page Info? Or in the plain-text message 
compposition? How about address book cards? ...
mass moving open bugs pertaining to view source to pmac@netscape.com as qa contact.

to find all bugspam pertaining to this, set your search string to
"ItsSharkeysNight".
QA Contact: sairuh → pmac

Updated

16 years ago
Component: Preferences → ViewSource
Summary: [RFE] Set View Source font family and size → Set View Source font family and size

Updated

16 years ago
Blocks: 143119
Product: Browser → Seamonkey
Assignee: doronr → mrbkap
QA Contact: pmac → doronr
Target Milestone: Future → ---

Comment 13

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 14

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 15

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 16

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 17

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 18

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 19

10 years ago
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Assignee: mrbkap → nobody
QA Contact: doronr → view-source

Comment 20

9 years ago
(In reply to comment #15)
> This bug report is registered in the SeaMonkey product, but has been without a
> comment since the inception of the SeaMonkey project. This means that it was
> logged against the old Mozilla suite and we cannot determine that it's still
> valid for the current SeaMonkey suite. Because of this, we are setting it to an
> UNCONFIRMED state.
> 
> If you can confirm that this report still applies to current SeaMonkey 2.x
> nightly builds, please set it back to the NEW state along with a comment on how
> you reproduced it on what Build ID, or if it's an enhancement request, why it's
> still worth implementing and in what way.
> If you can confirm that the report doesn't apply to current SeaMonkey 2.x
> nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME,
> INVALID, WONTFIX, or similar).
> If no action happens within the next few months, we move this bug report to an
> EXPIRED state.
> 
> Query tag for this change: mass-UNCONFIRM-20090614

(In reply to comment #19)
> This bug report is registered in the SeaMonkey product, but has been without a
> comment since the inception of the SeaMonkey project. This means that it was
> logged against the old Mozilla suite and we cannot determine that it's still
> valid for the current SeaMonkey suite. Because of this, we are setting it to an
> UNCONFIRMED state.
> 
> If you can confirm that this report still applies to current SeaMonkey 2.x
> nightly builds, please set it back to the NEW state along with a comment on how
> you reproduced it on what Build ID, or if it's an enhancement request, why it's
> still worth implementing and in what way.
> If you can confirm that the report doesn't apply to current SeaMonkey 2.x
> nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME,
> INVALID, WONTFIX, or similar).
> If no action happens within the next few months, we move this bug report to an
> EXPIRED state.
> 
> Query tag for this change: mass-UNCONFIRM-20090614

Hope I'm in the same category (newbie).  I receive a lot of email with hyperlinks.  Every time I click on one I have to reset the zoom size. I would like to be able to choose my own default size.  As long as I'm surfing, the zoom setting holds, of course. (Preference rather than "bug" really.

Comment 21

9 years ago
SeaMonkey trunk is now using toolkit viewsource.
Component: View Source → View Source
Product: SeaMonkey → Toolkit
QA Contact: view-source → view.source
You need to log in before you can comment on or make changes to this bug.